@article{Arbaoui2002,
annote = {Art\'{\i}culo de revista que hace una comparativa de los entornos de ingenier\'{\i}a del software process-centered.

        
Es un poco antigua y las herramienta que se presentan quiz\'{a}s no debieran ser tomadas en cuenta.

        
Lo m\'{a}s importante es que hace una enumeraci\'{o}n de los requisitos que deben de tener este tipo de herramientas.

      },
author = {Arbaoui, S and Derniame, JC and Oquendo, F and Verjus, H},
journal = {Annals of Software Engineering},
keywords = {comparative,enviroments,process-centered,tool requisites},
mendeley-tags = {comparative,enviroments,process-centered,tool requisites},
number = {1-4},
pages = {311 -- 340},
title = {{A Comparative Review of Process--Centered Software Engineering Environments}},
volume = {14},
year = {2002}
}
@article{Rolland1998,
annote = {Art\'{\i}culo que nos presenta clasifcionaciones de system development process engineering desde 4 puntos de vista (facets)

        

        
ES IMPORTANTE POR LAS CLASIFICACIONES E IDEAS QUE CONTIENE AUNQUE SEA VIEJO.

        
THE SUBJECT WORLD

        
Dice que el proceso es para obtener un producto (lo cu\'{a}l es una afirmaci\'{o}n en s\'{\i} misma importante) y dice que la en la propia comunidad hay varios puntos de vista de lo que debe ser un proceso

        
-Procesos estrat\'{e}gicos, t\'{a}cticos y de implementaci\'{o}n

        
THE USAGE WORLD

        
Para establecer los objetivos de los procesos. Tres dominios )el modelo del proceso, el perfomance, y el enactment)

        
A nivel de cobertura  puedo distinguir entre:
-Activity -oriented
-Product-oriented 
-Decision-oriented.

        
En cuanto a la granularidad hay que decibir a que nivel llego en la drescripci\'{o}n del proceso.

        
Luego tb la notaci\'{o}n

        
THE DEVELOPMENT WORLD

        

        
La conclusi\'{o}n que saca es que el la ingenier\'{\i}a de procesos debe ser USAGE DRIVEN

        
Es este apartado distingue tres tipos de objetivos en los modelos de procesos que es algo muy interesante y que merece la pena citar

        
-Modelo descripto
- Modelos prescriptivo
-Modelo explicativo.

        
THE SYSTEM WORLD
Para fijar qu\'{e} queremos representar, a qu\'{e} nivel de abstracci\'{o}n. c\'{o}mo se va a representar  y que propiedades deber\'{\i}a tener,

        

        

        

      },
author = {Rolland, C},
keywords = {classification,criteria,process},
mendeley-tags = {classification,criteria,process},
pages = {1 -- 24},
title = {{A Comprehensive View of Process Engineering}},
year = {1998}
}
@article{Oren2007,
author = {Oren, E and Haller, A and Hauswirth, M and Heitmann, B and Decker, S and Mesnage, C},
doi = {10.1109/MS.2007.126},
issn = {0740-7459},
journal = {IEEE Software},
keywords = {previo},
mendeley-tags = {previo},
number = {5},
pages = {64--71},
title = {{A Flexible Integration Framework for Semantic Web 2.0 Applications}},
url = {http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=4302688},
volume = {24},
year = {2007}
}
@inproceedings{Bravo2007,
address = {Munich},
annote = {Habla de la herramienta COLLECE que es una herramienta de programaci\'{o}n colaborativa para que varios personas editen, compilen y run a la vez....

        
Eval\'{u}a su eso....

        

      },
author = {Bravo, C. and Duque, R. and Gallardo, J. and Garc\'{\i}a, J. and Garc\'{\i}a, P.},
booktitle = {Proceeding for International Workshop on TOMAG+REMIDI},
keywords = {builing,code,collaboration,deploy,tool},
mendeley-tags = {builing,code,collaboration,deploy,tool},
pages = {59--},
publisher = {Center for Telematics and Information Technology (CTIT)},
title = {{A groupware System Distributed Collaborative Programming: Usability Issues and Lesson Learned}},
year = {2007}
}
@article{Chen2009,
abstract = {Change is inevitable in the software product lifecycle. When a software change occurs, all of the stakeholders and related artifacts should be considered in determining the success of the change action in a collaborative development environment such as JAD (joint application development). In this regard, current implementation-based or homogeneous impact analyses are insufficient; therefore, this paper presents a holistic approach to change impact analysis in handling not only software contents but also other items such as requirements, documents and data. This approach characterizes product contents and relates heterogeneous items by using attributes and linkages. It also uses an object-oriented propagation mechanism to handle dynamic looping in determining the impact of changes. A prototype, EPIC, was built to realize this approach and these concepts. A walkthrough example is provided in order to verify the work of the proposed approach. An empirical study is presented to discuss the benefits of the proposed approach and the application of EPIC in a software company. Lessons learned from the case study and improvement issues of the proposed approach and the tool are also discussed.},
annote = {Art\'{\i}culo muy interesante en relaci\'{o}n con la gesti\'{o}n de los cambios y la trazabilidad que presenta un metamodelo, una herramienta y un caso pr\'{a}ctico.

        
Presenta la problem\'{a}tica de la gesti\'{o}n del cambio

        
Presenta el problema de que los m\'{e}todos tradicionales no tienen en cuenta todos los artifacts

        
Y luego varios enfoques y un metamodelo 

        
Puede ser interesante...},
author = {Chen, Chung-Yang and Chen, Pei-Chi},
journal = {Journal of Systems and Software},
keywords = {change,management,traceability},
mendeley-tags = {change,management,traceability},
number = {12},
pages = {2051--2067},
title = {{A holistic approach to managing software change impact}},
url = {http://linkinghub.elsevier.com/retrieve/pii/S0164121209001654},
volume = {82},
year = {2009}
}
@article{Chazalet2009,
abstract = {Service-oriented computing (SOC) defines an application as an assembly of loosely coupled software elements: services. Nowadays, SOC is very technology-driven. Engineers have to deal with numerous technologies for describing, publishing services and creating and manipulating services applications. In particular, the deployment of serviceoriented applications is a complex task, restricted to experts. By deploying, we mean installing, activating, deactivating, maintaining and deinstalling. This paper presents a modeldriven approach for the context-aware deployment of service-oriented applications in constrained services execution environments. This approach is based on several deployment-oriented meta-models and has been implemented in a tool. This work has been validated on an industrial use case.},
annote = {Art\'{\i}culo que aunque no habla de la Tool Integration si que est\'{a} en cierta manera relacionado ya que el tema tratado son los sistemas pervasivos y los diferentes dispositivos que hay que integrar en estos sistemas.

        
Propone una herramienta basada en servicios para conseguir el despliegue de este tipo de aplicaciones.

        
Presenta 6 metamodelos relacionados con esta fase y que quiz\'{a}s puedan servirnos para otras.

        
Contiene referencias muy v\'{a}lidas sobre la fase de deploy.

      },
author = {Chazalet, Antonin and Lalanda, Philippe},
journal = {ICPS},
keywords = {DSDM,deployment,model,pervasive,service,tools},
mendeley-tags = {DSDM,deployment,model,pervasive,service,tools},
title = {{A model-driven environment for the deployment of pervasive service-oriented applications}},
url = {http://portal.acm.org/citation.cfm?id=1568227},
year = {2009}
}
@article{WICKS2007,
abstract = {This article highlights tool integration within software engineering environments. Tool integration concerns the techniques used to form coalitions of tools that provide an environment supporting some, or all, activities within a software engineering process. These techniques have been used to create environments that attempt to address aspects of software development, with varying success. This article provides a timely analysis and review of many of the significant projects in the field and, combined with evidence collected from industry, concludes by proposing an empirical manifesto for future research, where we see the need for work to justify tool integration efforts in terms of relevant socio-economic indicators.},
annote = {Articulo que hace un revisi\'{o}n de la literatura relacionada con tool integration

        
Dice que este tema ha estado en la literatura de 1980

        
Marca los retos del futuro en este tipo de investigaciones que son:

        
-Enlazar herramientas de diferentes fases del ciclo de desarrollo (completo)

        
Tiene un mont\'{o}n de referencias interesantes sobre tool integration.

        
Hace un an\'{a}lisis de 300 papers sobre este tema y los divide en descriptivos , formulativos y evaluativos.

        
Los descriptivos intentan describir el fen\'{o}meno.

        
Los formulativos se dividen en tres categor\'{\i}as PSEE-Based (lo que voy a tener en cuenta) XML/XMI y las novedades (Web Services?)

        
Los evaluativos de algunas propuestas y sus resultados (tambi\'{e}n en tres categor\'{\i}as)

        

        
Contiene una afirmaci\'{o}n muy importante que dice que la integraci\'{o}n total no se puede conseguir (pag 1577) 

        
En la p\'{a}gina 1578 presenta los objetivos que se deben buscar en este tipo de investigaci\'{o}n

        
Al final contiene un recopilaci\'{o}nde congresos relevantes sobre el tema y una bibliograf\'{\i}a impresionante sonre el tema.

      },
author = {WICKS, M and DEWAR, R},
journal = {Journal of Systems and Software},
keywords = {SLR,integration,tool},
mendeley-tags = {SLR,integration,tool},
month = sep,
number = {9},
pages = {1569--1585},
title = {{A new research agenda for tool integration☆}},
url = {http://dx.doi.org/10.1016/j.jss.2007.03.089},
volume = {80},
year = {2007}
}
@article{Biffl2009,
abstract = {In modern software application development, engineering systems and tools from several sources have to cooperate for building agile process environments. While there are approaches for the technical integration of component-based business software systems, there is only little work on the flexible and efficient integration of engineering tools and systems along the software life cycle. In this paper we introduce the concept of the “Engineering Service Bus” (EngSB) based on established Enterprise Service Bus concepts for business software systems. Based on real-world use cases from software engineering we show how the EngSB allows prototyping new variants of software engineering processes and derive research issues for further work.},
annote = {Congreso SOMET
Es un art\'{\i}culo que tiene mucho que ver con lo que estamos buscando.

        
Plantean los retos que surgen en el mundo del SaaS (Software as Sevice).

        
En ese entorno actual para conseguir automatizaci\'{o}n y calidad es necesaria una integraci\'{o}n de los sistemas y sem\'{a}ntica.

        
Esto prentede conseguirlo con la utilizaci\'{o}n de un ESB (que es m\'{a}s o menos lo que queremos nosotros) con una seri de caractr\'{\i}sticas que son casi calcadas de lo que se prentende en el art\'{\i}culo de Schawber.

        
Dedica un cap\'{\i}tulo a hacer un resumen de los enfoques actuales.

        
Un punto importante  es que habla de los escenarios importantes para la tool integration que son precisamente de los que habla Schawber.

        
Para eso el EsB normal tiene ciertas limitaciones y por eso por eso propone el engESB que llama \'{e}l. 

        
Propone una arquitectura donde uno de los conceptos importantes es el conector y habla de cosas similares a Jazz para la integraci\'{o}n de distintos modelos entre las difentes herrramientas.

        

      },
author = {Biffl, Stefan and Schatten, Alexander},
journal = {Frontiers in Artificial Intelligence and Applications; Vol. 199},
keywords = {ESB,architecture,integration,services},
mendeley-tags = {ESB,architecture,integration,services},
title = {{A Platform for Service-Oriented Integration of Software Engineering Environments}},
url = {http://portal.acm.org/citation.cfm?id=1659316},
year = {2009}
}
@misc{Zhuge2004,
abstract = {Integration of Web Services for large-scale applications concerns complex processes. Component technology is an important way to decompose a complex process and promote efficiency and quality. This paper proposes a service integration approach considering both the integration of service flows and the integration of data flows. The approach includes the component-based Web Service process definition tool, mechanism for retrieving services in a well-organized service space and UDDI repositories, algorithms for heterogeneous data flow integration, and rules for service verification. The proposed approach has been integrated into an experimental service platform and used in an online book sale business application. Comparisons show the features of the proposed approach.},
annote = {Art\'{\i}culo que habla sobre la integraci\'{o}n de los diferentes tipos de datos proporcionados por diferentes servicios

        
Propone una soluci\'{o}n basada en mapeados   una arquitectura de integraci\'{o}n entre el esquema global y el esquema origen .

        
Construye una herramienta y un ejemplo para verificar lo enunciado

      },
author = {Zhuge, Hai and Liu, Jie and Ding, Lianhong and Chen, Xue},
booktitle = {Grid and Cooperative Computing},
doi = {10.1007/b97163},
isbn = {978-3-540-21993-4},
keywords = {architecture,data,integration,semantic,services,tool},
mendeley-tags = {architecture,data,integration,semantic,services,tool},
pages = {787--794},
publisher = {Springer Berlin / Heidelberg},
title = {{A Semantic-Based Web Service Integration Approach and Tool}},
url = {http://www.springerlink.com/content/l2ud41ng5qh7cmt7/},
volume = {3033/2004},
year = {2004}
}
@article{,
keywords = {education,services},
mendeley-tags = {education,services},
title = {{Adoption of Service Oriented Architecture (SOA) for Enterprise Systems in Education: Recommended Practices}},
year = {2009}
}
@article{Goth2009,
annote = {Breve art\'{\i}culo que presenta un poco la situaci\'{o}n de crecimiento de las empresas que trabajan con metodolog\'{\i}as \'{a}giles y c\'{o}mo afrontan su paso a enfoques ALM. Lo m\'{a}s interesente es la lista de aplicaciones "ALM" que presenta.},
author = {Goth, G.},
journal = {IEEE Software},
keywords = {ALM,agile,application,lifecycle,management,tools},
mendeley-tags = {ALM,agile,application,lifecycle,management,tools},
number = {2},
pages = {88--91},
title = {{Agile Tool Market Growing with the Philosophy}},
url = {http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=4786959},
volume = {26},
year = {2009}
}
@misc{Asuncion2006,
abstract = {Traceability is a critically important aspect of software development that is often required by various professional standards and government agencies. Yet, current approaches do not adequately address end-toend traceability. Consequently, many industry projects become entangled in process overhead and fail to derive much benefit from current traceability solutions. This paper presents a successful end-to-end software traceability tool developed at Wonderware, a software development company and a business unit of Invensys Systems, Inc. Our process-oriented approach achieves comprehensive traceability and supports the entire software development life cycle by focusing on both requirements traceability and process traceability. This paper offers general traceability guidelines that have emerged from the experience of implementing and deploying this traceability tool within actual company constraints. We discuss encouraging preliminary results and point to the advantages gained in using our approach.},
address = {Irvine},
annote = {GeDice que tenemos dos tipos de trazabilidad de proceso y de requisitos

        
Dice que normalmente lo conseguido es la trazabilidad entre dos fases pero lo que se busca es la trazabilidad a lo largo de todo el ciclo de vida entrelazada con el proceso

        
Implementa una herramienta basad en un modelo de trazabilidad y luego se dedica a hacer una presentaci\'{o}n.

        
Puede servir como referencia para el concepto de trazabilidad, o al menos como punto de partida.

        

      },
author = {Asuncion, Hazeline and Fran\c{c}ois, Fr\'{e}d\'{e}ric and Taylor, Richard N.},
file = {::},
institution = {Institue of Software Research (ISR)},
keywords = {model,tool,traceability},
mendeley-tags = {model,tool,traceability},
title = {{An End-To-End Software Traceability Tool in an Industrial Context}},
url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.79.1227},
year = {2006}
}
@article{Webster2002,
abstract = {A review of prior, relevant literature is an essential feature of any academic project. An effective review creates a firm foundation for advancing knowledge. It facilitates theory development, closes areas where a plethora of research exists, and uncovers areas where research is needed. In the information systems (IS) field, we see few published review articles. As a result, the progress of our field is impeded. To address this concern, the MIS Quarterly launched MISQ Review several years ago. The clear intention was to accelerate the accumulation of IS knowledge. A particular goal was to advance the state of theory within the IS field. The stated purpose of MISQ Review is to \ldots promote MIS research by publishing articles that conceptualize research areas and survey and synthesize prior research. These articles will provide important input in setting directions for future research. 1 The lack of theoretical progress in the IS field may be surprising. From an empirical viewpoint, the IS field resembles other management fields. Specifically, as fields of inquiry develop, their theories are often placed on a hierarchy from ad hoc classification systems (in which categories are used to summarize empirical observations), to taxonomies (in which the relationships between the categories can be described), to conceptual frameworks (in which propositions summarize explanations and predictions), to},
annote = {Dice que lo esencial de una SLR es detectar nuevas \'{a}reas de investigaci\'{o}n.

        
la IS es una \'{a}rea j\'{o}ven y multidisciplinar.

        
La introducci\'{o}n de una SLR debe ser clara y motivadora (caracter\'{\i}sticas ALM 2.0)

        
Hay que definir bien las variables y los l\'{\i}mites

        
Concept-centered 

        
Define el proceso empezando por las fuentes principales

        
Dice que no funciona la orientaci\'{o}n author-centric.

        
Propone las tablas como mejor soluci\'{o}n

        
Tono constructivo (tiene una cita muy buena para justificar eso) y tolerante a fallos.

        
La redacci\'{o}n salvo eolvuci\'{o}n de opiniones debe ser en tiempo presente.

        
Justificar la propuestas resultantes es lo m\'{a}s dif\'{\i}cil

      },
author = {Webster, Jane and Watson, Richard T.},
file = {::},
journal = {MIS QUarterly},
keywords = {SLR},
mendeley-tags = {SLR},
pages = {13--23},
publisher = {MIS Quarterly},
title = {{Analyzing the past to prepare for the future: Writing a literature review}},
url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.104.6570},
volume = {26},
year = {2002}
}
@article{Aalst2003,
abstract = {Business Process Management (BPM) includes methods, techniques, and tools to support the design, enactment, management, and analysis of operational business processes. It can be considered as an extension of classical Workflow Management (WFM) systems and approaches. Although the practical relevance of BPM is undisputed, a clear definition of BPM and related acronyms such as BAM, BPA, and STP are missing. Moreover, a clear scientific foundation is missing. In this paper, we try to demystify the acronyms in this domain, describe the state-of-the-art technology, and argue that BPM could benefit from formal methods/languages (cf. Petri nets, process algebras, etc.).},
annote = {Un art\'{\i}culo que tiene definiciones a tener en cuenta para citar en los art\'{\i}culos:

        
-Business Process
-Process-Aware 
-BAM

        
Presenta como reto la integraci\'{o}n en la p\'{a}gina 3 y en la misma p\'{a}gina presenta el cambio de orientaci\'{o}n de data-centered a process-centered.

        
Habla de las tecnolog\'{\i}as relacionadas.

        
Habla de las tres fases de BMP

        
Habla que hay que tener en cuenta la sem\'{a}ntica de las notaciones cuando selecciones una herramienta. 

      },
author = {Aalst, Wil M. P. Van Der and Hofstede, Arthur H. M. Ter and Weske, Mathias},
journal = {Lecture Notes In Computer Science},
keywords = {business,management,process,workflow},
mendeley-tags = {business,management,process,workflow},
pages = {1--12},
title = {{Business process management: a survey}},
url = {http://portal.acm.org/citation.cfm?id=1761141.1761143},
year = {2003}
}
@article{Dustdar2004,
annote = {se centra en equipos de desarrollo mixtos (gente de fuera y de dentro de la empresa)  y distribuidos.

        
INtroduce en ese campo donde es muy necesaria la colaboraci\'{o}n el concept de process-awarenesss que significa que se requiere informaci\'{o}n del estado de todas las actividades de los miembros del proyecto.

        

        
Propone dentro de una herramienta una organizaci\'{o}n de equipos, un modelador de tareas y actividades y un planificador etc.

        
Para ello propone un arquiteectura para no habla nada de integraci\'{o}n aunque puede ser bueno echar un ojo a esta arquitectura.

        

      },
author = {Dustdar, S},
journal = {Distributed and Parallel Databases},
keywords = {architecture,collaboration,groupware,interaction managemet,knowledge logistics,process,process-aware collaboration,tool,virtual teams,workflow},
mendeley-tags = {architecture,collaboration,process,tool,workflow},
number = {1},
pages = {45 -- 66},
title = {{Caramba---A Process-Aware Collaboration System Supporting Ad hoc and Collaborative Processes in Virtual Teams}},
volume = {15},
year = {2004}
}
@article{Engels2001,
annote = {Cita las ventajas de los entornos process-centered y la principal desventaja: las costumbres  de los desarrolladores.

        
Define muy bien lo que es un PCSEE y las caracter\'{\i}sticas que tiene que tener (flexibilidad, intgraci\'{o}n y centrarse en un rango de procecos)

        
Para finalizar marca un serie de tendencias futuras (el art\'{\i}culo es del 2003)

        
-Distintas partes del proces distintos mecanismos
-Hay que fomentar la colaboraci\'{o}n en el equipo
-El modelo del proceso puede ser un par\'{a}metro)
-El equipo puede ser distribuido.

      },
author = {Engels, G and Schafer, W},
keywords = {process,process-centered enviroments,software engineering,software process},
mendeley-tags = {process},
pages = {671 -- 675},
title = {{Challenges and Achievements in Software Engineering (CHASE)}},
year = {2001}
}
@article{Muller,
annote = {Cap\'{\i}tulo de revista antique sobre actividades participativas en el proceso de desarrollo de software . Fija la situaci\'{o}n ideal hablando de interdisciplinariedad, de participaci\'{o}n de todos los participante etc...

        
Contrapone m\'{e}todos formales o m\'{e}todos participativas aunque en un momento dado habla de la posibilidad de mezclarlos. 

        
Presenta tambi\'{e}n los posibles problemas del trabajo colaborativo o participativo

        
Para finalizar presenta una lista resumida (indicando la fase del proceso de desarrollo en la que se puede aplicar) de pr\'{a}cticas participativas en el desarrollo del software.

        

      },
author = {Muller, Michael J. and Haslwanter, Jean Hallewell and Dayton, Tom},
keywords = {participatory},
mendeley-tags = {participatory},
title = {{Challenges and Achievements in Software Engineering (CHASE)}}
}
@inbook{Betz2007,
annote = {cap\'{\i}tulo de libro que presenta una alternativa a CMMI e ITIL. },
author = {Betz, Charles T.},
booktitle = {Architecture and Patterns for IT Service Management, Resource Planning, and Governance},
keywords = {CMMI,ITIL,management,service},
mendeley-tags = {CMMI,ITIL,management,service},
pages = {35--108},
publisher = {Elsevier},
title = {{Chapter 2 - The IT Value Chain }},
year = {2007}
}
@inbook{Betz2007a,
annote = {cap\'{\i}tulo de libro que presenta una alternativa a CMMI e ITIL.

        
Presenta varios conceptos valiosos:

        
- Funci\'{o}n vs Proceso

        
-Cita un est\'{a}ndar OMG para reusabilidad que quiz\'{a}s ser\'{\i}a interesante bajarse.

        
-Presenta el concepto de ALM tal  y como lo conocemos incluso con gr\'{a}ficos similares a los de Schawber

        
-Presenta en concepto de mapa de integraci\'{o}n y gesti\'{o}n de la integraci\'{o}n

        
Y lo que tendremos que tener en cuenta son las \'{a}reas para systems solutions delivery

        
Para acabar presenta una arquitectura ideal

      },
author = {Betz, Charles T.},
booktitle = {Architecture and Patterns for IT Service Management, Resource Planning, and Governance },
keywords = {CMMI,ITIL,management,service},
mendeley-tags = {CMMI,ITIL,management,service},
pages = {227--305},
publisher = {Elsevier},
title = {{Chapter 4 - A supporting Systems Architecture}},
year = {2007}
}
@article{Barthelmess2003,
annote = {Recoge la necesidad de colaboraci\'{o}n e integraci\c{c}on en los entornos de desarrollo de software.

        
Dice que la calidad del producto depende de la calidad del proceso

        
Enuncia una de las caracter\'{\i}sticas m\'{a}s importante del proceso de desarrollo: creativo, human-centered; sujeto a cambios continuos.

        

        
Define Process MOdel, Artifact, Role y Enviroment.

        
El resto tiene algunas cosas m\'{a}s pero que son repetidos en otor art\'{\i}culos que ya he visto.

        

        

        

        

      },
author = {Barthelmess, P},
journal = {Information and Software Technology},
keywords = {PCSDE,collaboration,communication,process},
mendeley-tags = {PCSDE,collaboration,communication,process},
pages = {911 -- 928},
title = {{Collaboration and Coordination in Process--Centered Software Development Environments: A Review of the Literature}},
volume = {45},
year = {2003}
}
@unpublished{Reinhardt,
annote = {Habla de la importancia de la comunicaci\'{o}n entre los diferentes actores involucrados en las fases de desarrollo de software y de aplicaci\'{o}n de twitter para ello.
Presenta un par de diagramas importantes sobre la compartici\'{o}n de conocimientos. y el tri\'{a}ngulo tecnolog\'{o}cio

      },
author = {Reinhardt, W.},
file = {::},
institution = {University of PaderBorn, Institute of Computer Science},
keywords = {client,collaboration,eclipse,lifecycle,social,tool,twitter},
mendeley-tags = {client,collaboration,eclipse,lifecycle,social,tool,twitter},
title = {{Communication is the key – Support Durable Knowledge Sharing in Software Engineering by Microblogging}}
}
@inproceedings{Niinimaki2007,
address = {Munich},
annote = {Habla de la complejidad del proceso de desarrollo de software y de la importancia del tailoring en cada proyecto as\'{\i} como de las la gran cantidad de comunicaci\'{o}n y colaboraci\'{o}n que se produce (que es lo que se pretende mejorar)

        
No tiene mucho de interesante para el resto de la investigaci\'{o}n

        

        

        

      },
author = {Niinim\"{a}ki, T.},
booktitle = {Proceeding for International Workshop on TOMAG+REMIDI},
keywords = {collaboration},
mendeley-tags = {collaboration},
pages = {53--58},
publisher = {Centers for Telematics and Information Technology (CTIT)},
title = {{Communication Tools in Globally Distributed Software Development Project}},
year = {2007}
}
@book{Ziegler2007,
abstract = {Data integration is one of the older research fields in the database area and has emerged shortly after database systems were first introduced into the business world. In this paper, we briefly introduce the problem of integration and, based on an architectural perspective, give an overview of approaches to address the integration issue. We discuss the evolution from structural to semantic integration and shortly present our own research in the SIRUP (Semantic Integration Reflecting User-specific semantic Perspectives) approach. Finally, an outlook to challenging areas of future research in the realm of data integration is given.},
address = {Berlin, Heidelberg},
annote = {cultura general sobre integraci\'{o}n de datos con los problemas que hay y los diferentes enfoques que podemos abordar.

        
Tb habla de los problemas de la integraci\'{o}n sem\'{a}ntica y de abordad estos problemas con ontolog\'{\i}as y/o multi-ontolog\'{\i}as.

      },
author = {Ziegler, Patrick and Dittrich, Klaus},
booktitle = {Conceptual Modelling in Information Systems Engineering},
doi = {10.1007/978-3-540-72677-7},
isbn = {978-3-540-72676-0},
keywords = {data,integration,semantic},
mendeley-tags = {data,integration,semantic},
pages = {39--58},
publisher = {Springer Berlin Heidelberg},
title = {{Conceptual Modelling in Information Systems Engineering}},
url = {http://www.springerlink.com/index/10.1007/978-3-540-72677-7},
year = {2007}
}
@article{Vinoski1997,
abstract = {This paper will appear in the feature topic issue of the IEEE Communications Magazine, Vol. 14, No. 2, February 1997. It is presented in this format to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by the author and by other copyright holders. All persons copying this informationare expected to adhere to the terms and constraints invoked by the author's copyright. In most cases, this work may not be reposted without the explicit permission of the copyright holder. 1 Introduction},
annote = {Art\'{\i}culo antiguo que explica a grandes rasgos el prop\'{o}sito y las caracter\'{\i}sticas de CORBA. Si que justifica la integraci\'{o}n al hablar de heterogeneidad de sistemas.

      },
author = {Vinoski, Steve},
journal = {IEEE Communications Magazine},
keywords = {corba,integration},
mendeley-tags = {corba,integration},
pages = {46--55},
title = {{CORBA: Integrating Diverse Applications Within Distributed Heterogeneous Environments}},
url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.42.4576},
volume = {14},
year = {1997}
}
@article{Kitchenham2007a,
annote = {Art\'{\i}culo que eval\'{u}a la realizaci\'{o}n de una SLR. Tiene muy pocas cosas nuevas lo que si merece la pena es una serie de afirmaciones y definiciones generales que se pueden usar para fundamentar una SLR.

        
Establece una fase primaria de la SLR y una secundaria que revisa las referencias o bibliograf\'{\i}a de la primario (yo de momento no he hecho esto)

        
Habla de contactar con los autores y establece unos criterios para medir la calidad de los art\'{\i}culos revisador.

      },
author = {Kitchenham, Barbara A. and Mendes, Emilia and Travassos, Guilherme H.},
journal = {IEEE Transactions on Software Engineering},
keywords = {RSL,SLR},
mendeley-tags = {RSL,SLR},
month = may,
number = {5},
pages = {316--329},
publisher = {Published by the IEEE Computer Society},
title = {{Cross versus Within-Company Cost Estimation Studies: A Systematic Review}},
url = {http://www.computer.org/portal/web/csdl/doi/10.1109/TSE.2007.1001},
volume = {33},
year = {2007}
}
@book{Grefen2002,
abstract = {Workflows have generally been accepted as a means to model and support processes in complex organizations. The fact that these
  processes require robustness and clear semantics has generally been observed and has lead to the combination of workflow and
  transaction concepts. Many variations on this combination exist, leading to many approaches to transactional workflow support.
  No clear classification of these approaches has been developed, however, resulting in a badly understood field. To deal with
  this problem, we describe a clear taxonomy of transactional workflow models, based on the relation between workflow and transaction
  concepts. We show that the classes in the taxonomy can directly be related to specification language and architecture types
  for workflow and transaction management systems. We compare the classes with respect to their characteristics and place existing
  approaches in the taxonomy - thus offering a basis for analysis of transactional workflow support.},
address = {Berlin, Heidelberg},
annote = {Art\'{\i}culo que compara los conceptos siguientes:

        
-Transactional Workflows
-Workflow Transactions

        
No sirve de mucho aunque nos puede servir como justificaci\'{o}n adicional a la hora de elegir un tipo de herramienta

      },
author = {Grefen, Paul},
booktitle = {Database and Expert Systems Applications},
doi = {10.1007/3-540-46146-9},
editor = {Hameurlain, Abdelkader and Cicchetti, Rosine and Traunm\"{u}ller, Roland},
isbn = {978-3-540-44126-7},
keywords = {transaction,workflow},
mendeley-tags = {transaction,workflow},
month = aug,
pages = {327--349},
publisher = {Springer Berlin Heidelberg},
series = {Lecture Notes in Computer Science},
title = {{Database and Expert Systems Applications}},
url = {http://www.springerlink.com/content/jf42833rutvtexdt},
volume = {2453},
year = {2002}
}
@phdthesis{HenriElemo2008,
annote = {Tiene mucho de cultura general relacionada con SCM y los componentes relacionados.

        
Concibe SCM y la gesti\'{o}n y el cambio como procesos (lo cu\'{a}l es importante) y lo relaciona con las distintas \'{a}reas del ciclo de vida.

        
Eval\'{\i}a diferente herramientas en base a una serie de requisitos que deber\'{\i}a tener el SCM y presenta una tablas trabajadas al respecto

        

      },
author = {{Henri Elemo}},
file = {::},
keywords = {change,configuration,management,process},
mendeley-tags = {change,configuration,management,process},
pages = {87},
school = {Helsinki University of Technology},
title = {{DEFINING SOFTWARE CONFIGURATION MANAGEMENT}},
year = {2008}
}
@book{Rathfelder2008,
abstract = {The implementation of an enterprise-wide Service Oriented Architecture (SOA) is a complex task. In most cases, evolutional approaches are used to handle this complexity. Maturity models are a possibility to plan and control such an evolution as they allow evaluating the current maturity and identifying current shortcomings. In order to support an SOA implementation, maturity models should also support in the selection of the most adequate maturity level and the deduction of a roadmap to this level. Existing SOA maturity models provide only weak assistance with the selection of an adequate maturity level. Most of them are developed by vendors of SOA products and often used to promote their products. In this paper, we introduce our independent SOA Maturity Model (iSOAMM), which is independent of the used technologies and products. In addition to the impacts on IT systems, it reflects the implications on organizational structures and governance. Furthermore, the iSOAMM lists the challenges, benefits and risks associated with each maturity level. This enables enterprises to select the most adequate maturity level for them, which is not necessarily the highest one.},
address = {Berlin, Heidelberg},
annote = {Presenta un nuevo modelo de madurez SOA},
author = {Rathfelder, Christoph and Groenda, Henning},
booktitle = {Distributed Applications and Interoperable Systems},
keywords = {Maturity,Model,SOA},
mendeley-tags = {Maturity,Model,SOA},
pages = {1--15},
publisher = {Springer Berlin Heidelberg},
series = {Lecture Notes in Computer Science},
title = {{Distributed Applications and Interoperable Systems}},
url = {http://www.springerlink.com/index/10.1007/978-3-540-68642-2},
volume = {5053},
year = {2008}
}
@misc{Shields2008,
annote = {No aporta mucho y \'{u}nicamente nos puede servir para a\~{n}adir justificaciones al uso y aplicaci\'{o}n de los enfoques BPM

      },
author = {Shields, Robert},
file = {::},
institution = {Telelogic},
keywords = {bpm,justify},
mendeley-tags = {bpm,justify},
title = {{Enabling Enterprise Business Process Management}},
year = {2008}
}
@unpublished{Geisser2007,
address = {Manheim},
annote = {Incide en la importancia cr\'{\i}tica de la fase de requisitos.

        
Enumera y explica las distintas fases de la fase de requisitos y en el cap\'{\i}tulo 3 enumera una serie de requisitos que seg\'{u}n Wiegers (1999), que es una referencia bibliogr\'{a}fica,  debe de tener una herramienta para la gesti\'{o}n de requisitos.

        
Y luego eval\'{u}a una serie de herramientas para la gesti\'{o}n de requisitos:

        
-IBM requisite Pro
-Serena RTM
-BorlanCaliberRM
-Telelogic DOORS

      },
author = {Geisser, M. and Tobias, H. and Riegel, N.},
file = {::},
institution = {University of Mannheim},
keywords = {evaluation,management,requirements,tools},
mendeley-tags = {evaluation,management,requirements,tools},
series = {Working Papers in Information Systems},
title = {{Evaluating the Applicability of Requirements Engineering Tools for Distributed Software Development}},
year = {2007}
}
@inproceedings{Biffl2009a,
annote = {M\'{e}todo para evaluar herramientas CASE basada en 5 familias de criterios. T\'{e}cnicos , de administraci\'{o}n , de capacidad de modelado, de generaci\'{o}n de c\'{o}digo, de procedimiento.
No queda muy claro como asigna los pesos para la evaluaci\'{o}n

      },
author = {Biffl, S. and Ferstl, C. and H\"{o}llwieser, C. and Moser, T.},
booktitle = {Procceeding of the 11th International Conference on Enterprise Information Systems (ICEIS 2009)},
file = {::},
keywords = {CASE,CASE TOOLS,Evaluate,Evalution,Multi-criteria,Open,Source},
mendeley-tags = {CASE,Evaluate,Multi-criteria},
pages = {41--49},
title = {{Evaluation of Case Tool Methos and Processes}},
year = {2009}
}
@phdthesis{Larsen,
annote = {No aporta mucho pero contiene muchas justificaciones de car\'{a}cter general para lo que estoy investigando y me puede servir.

        
Relaciona la calidad del Software con la calidad del proceso lo cu\'{a}l es una afirmaci\'{o}n muy importante.

        
Eval\'{u}a EPF y para ello establece una serie de criterios y eval\'{u}a OpenUp y tambi\'{e}n establece una serie de crierios para evaluar metodolog\'{\i}as.

        
Definici\'{o}n de PSEE y elementos relacionados (cultura general que siempre viene bien)

        
Y luego cita una serie de herramientas.

      },
author = {Larsen, S.},
file = {::},
keywords = {EPF,evaluation,justify,process,tools},
mendeley-tags = {EPF,evaluation,justify,process,tools},
school = {NTNU - Norwegian UNiversity of Science and Technology},
title = {{Evaluation of software process modelling tools for agile and industrial processes}}
}
@article{Ouyang2009,
author = {Ouyang, Chun and Dumas, Marlon and {Van Der Aalst}, Wil and {Ter Hofstede}, Arthur and Mendling, Jan},
doi = {10.1145/1555392.1555395},
issn = {1049331X},
journal = {ACM Transactions on Software Engineering and Methodology},
keywords = {previo},
mendeley-tags = {previo},
number = {1},
pages = {1--37},
title = {{From business process models to process-oriented software systems}},
url = {http://portal.acm.org/citation.cfm?doid=1555392.1555395},
volume = {19},
year = {2009}
}
@misc{Cherian2007,
annote = {En un proyecto fin de carrera del MIT
Su objetivo es analizar los factores  que hacer que la aplicaci\'{o}n de proporcionar de manera global servicios IT

        
Referencia el libro "The World is flat" que tengo que releear.

        
Hace un repaso hist\'{o}rico de la evoluci\'{o}n de los modelos operacionales en servicios IT basado en la localizaci\'{o}n geogr\'{a}fica. (esto pues servir algo para referenciarlo)

        
Adem\'{a}s de los beneficios del GDM cuando se refiere a los retos que tiene tiene algunos comunes con ALM Pg 38)

        
Propone una herramienta para evaluar estos modelos de GD

      },
author = {Cherian, Binoy},
institution = {MIT - Massachusetts Institute of Technology},
keywords = {economy,framework,impact,services,tools},
mendeley-tags = {economy,framework,impact,services,tools},
pages = {99},
title = {{Global Delivery of IT Services}},
year = {2007}
}
@article{Runeson2009,
abstract = {Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors' own experience from conducting and reading case studies. The terminology and guidelines are compiled from different methodology handbooks in other research domains, in particular social science and information systems, and adapted to the needs in software engineering. We present recommended practices for software engineering case studies as well as empirically derived and evaluated checklists for researchers and readers of case study research.},
annote = {Paper que a\'{u}n no he le\'{\i}do pero que tendr\'{\i}a que leer porque presenta una metodolog\'{\i}a para hacer estudios emp\'{\i}ricos en el mundo de la ingenier\'{\i}a del software.

      },
author = {Runeson, Per and H\"{o}st, Martin},
journal = {Empirical Software Engineering},
keywords = {case,methodology,research,study},
mendeley-tags = {case,methodology,research,study},
number = {2},
pages = {131},
title = {{Guidelines for conducting and reporting case study research in software engineering}},
url = {http://portal.acm.org/citation.cfm?id=1519313.1519324},
volume = {14},
year = {2009}
}
@article{Kitchenham2007,
annote = {Revisi\'{o}n del 2004 del documento base de Kitchenham},
author = {Kitchenham, Barbara and Charters, Stuart},
keywords = {SLR},
mendeley-tags = {SLR},
number = {EBSE 2007-001},
title = {{Guidelines for performing Systematic Literature Reviews in Software Engineering}},
url = {http://www.citeulike.org/user/akom/article/3955888},
year = {2007}
}
@book{Weiß2009,
abstract = {Software engineering traditionally plays an important role among the different research directions located in the Software
  Park Hagenberg, as it provides the fundamental concepts, methods and tools for producing reliable and high quality software.
  Software engineering as a quite young profession and engineering discipline is not limited to focus on how to create simple
  software programs, but in fact introduces a complex and most of the time quite costly lifecycle of software and derived products.
  Some efforts have been made to define software engineering as a profession and to outline the boundaries of this emerging
  field of research [PP04, Som04]. Several different definitions of the term software engineering appeared since its first mentioning
  on a NATO Software Engineering Conference in 1968.},
address = {Berlin, Heidelberg},
annote = { sobre Tiene cosas interesantes al principio pero luego es una mera recopilaci\'{o}n. No estar\'{\i}a de m\'{a}s tenerlo como referencia sobre los asuntos que recopilar.

        
Vuelve a establecer (pg 160) la imposibilidad de ser (dado la complejidad del proceso de desarrollo de software) totalmente prescriptivo (definirlo totalmente de manera previa)

        
Cita las actividades claves para el process management ylos objetivos que se persiguen con esa tarea.

        
Relaciona tambi\'{e}n la calidad del desarrollo con la calidad del proceso (pg 164)

        
Cita varios est\'{a}ndares CMMI la ISO 1227

        
Cita los retos del SW Process Engineering (pg 170)

        
Abre la puerta a la aplicaci\'{o}n del concepto de SPL en este campo.

        
Cita los problemas de la integraci\'{o}n (pg 173) y para dar soluci\'{o}n a esto surge el concepto de ALM con lo que aporta o lo que debe aportar ALM (coincide con muchos estudios leidos)

        
Hace un repaso general de la SW Quality del Testing, Monitoring y tecnolog\'{\i}as relacionadas con ALM.

        
Puede ser importante como punto de informaci\'{o}n general.

        

        

      },
author = {Wei\ss, Gerhard and Pomberger, Gustav and Beer, Wolfgang and Buchgeher, Georg and Dorninger, Bernhard and Pichler, Josef and Pr\"{a}hofer, Herbert and Ramler, Rudolf and Stallinger, Fritz and Weinreich, Rainer},
booktitle = {Hagenberg Research},
editor = {Buchberger, Bruno and Affenzeller, Michael and Ferscha, Alois and Haller, Michael and Jebelean, Tudor and Klement, Erich Peter and Paule, Peter and Pomberger, Gustav and Schreiner, Wolfgang and Stubenrauch, Robert and Wagner, Roland and Wei\ss, Gerhard and Windsteiger, Wolfgang},
keywords = {alm,general,integration,management,problems,process},
mendeley-tags = {alm,general,integration,management,problems,process},
pages = {157--235},
publisher = {Springer Berlin Heidelberg},
title = {{Hagenberg Research}},
url = {http://www.springerlink.com/content/n82404r9ju755141},
year = {2009}
}
@article{Oberhauser2007,
abstract = {Supply chains are a significant concept for improving the cooperation of vendors and customers for material products. While the assembly of increasingly complex components in modern software development resembles a supply chain, classical supply chain management concepts are rarely applied. An interruption in the flow of information exists between the development/maintenance phases and operational phases, resulting in ignorance, inefficiencies, and suboptimal quality and support levels. One reason for this is the effort necessary to integrate the software lifecycle processes, coupled with the dispersion of information needed for execution of (semi-)automated software lifecycle workflows across semantically heterogeneous sources. Furthermore, the manual derivation of abstract IT (e.g., ITIL) and software processes into concrete processes and workflows results in low quality and inefficiencies. This paper describes an approach for improving the integration of software supply chains via the (semi- )automated realization of abstract software lifecycle processes and workflows in conjunction with Semantic Web technologies.},
annote = {Art\'{\i}culo interesante que a\~{n}ade un enfoque sem\'{a}ntico a la integraci\'{o}n dentro del proceso del ciclo de vida del software.

        
Distingue 2 tipos de informaci\'{o}n que se genera en tiempo de ejecuci\'{o}n (runtime) 

        
Habla de las caracter\'{\i}sticas deseables que debiera de tener este tipo de soluci\'{o}n:

        
-Platform Independiente
-Vendor-Neutral
- Utilizar est\'{a}ndares
- Flexible y pobremente acoplado

        
Y tambi\'{e}n hace referencia a los principos de la soluci\'{o}n y a que tipos de integraci\'{o}n hay que conseguir (humanos, procesos, servicios etc..)

        
Utiliza un enqoeu de web sem\'{a}ntica para conseguir la integraci\'{o}n entre capas.

        
Justifica la utilizaci\'{o}n de motores de reglas.

        
Puede ser la base para relacionarlo con est\'{a}ndares relacionados como Ontolog\'{\i}as.

        
Introduce un nuevo t\'{e}rmino: ECM (Enterprise Content management) que habr\'{a} que tener en consideraci\'{o}n)

        

      },
author = {Oberhauser, Roy and Schmidt, Rainer},
file = {::},
journal = {ICSEA (International Conference on Software Engineering Advances)},
keywords = {alm,integration,runtime,semantic},
mendeley-tags = {alm,integration,runtime,semantic},
pages = {79},
title = {improving the integration of the software supply chain via the semantic web},
url = {http://portal.acm.org/citation.cfm?id=1304609.1306394},
year = {2007}
}
@article{Figay2009,
abstract = {Within the current economic context, enterprises are facing new interoperability issues due to increasing needs of eBusiness Collaboration within the emerging digital ecosystems they belong to. They also need to be able to keep in pace with their heterogeneous internal legacy systems. In addition, they should not have to modify their infrastructure or applications for fast and short collaboration implying information and knowledge interchange with new partners of their ecosystem. Current solutions are less and less adapted to face increasing needs and complexity. As proposing a new disruptive approach and technologies is inappropriate, this paper presents how to build enterprise application interoperability framework based on simultaneous and coherent usage of eBusiness standards used by a given ecosystem, combining usage of the different relevant frameworks supporting these standards. The goal is achievement of "pragmatic" interoperability. For the proposed approach, we consider simultaneous usage of Model Driven Engineering, Enterprise Modeling and Service Oriented Architecture. We also promote systematic usage of commodities on the WEB based on open and governed standards. Doing so, we have to solve issues related to semantic preservation, all along the lifecycle of the artifacts and infrastructures required to define and exploit an application. We introduce for that the concept of Extended Hypermodels and associated grounds.},
annote = {No es muy interesante pero contiene algunas tablas con descripciones importantes y un posible arquitectura.

        
Cita como siempre la base de la soluci\'{o}n a los problemas de integraci\'{o}n (modelos+servicios) y porque hay que solucionarlos.

        
Tabla de caracter\'{\i}sticas de los sistemas colaborativos ideales.

        
Tabla de los problemas de interoperabilidad

        
Tabla de principios y buenas pr\'{a}cticas relacionadas con interoperabilidad.

        
Arquitectura propuesta que presenta problemas y para inttroduce el concepto de Hipermodelo que puede ser importante

        

        

        

        

      },
author = {Figay, Nicolas and Ghodous, Parisa},
file = {::},
journal = {International Conference on Management of Emergent Digital EcoSystems},
keywords = {alm,framework,hypermodel,interoperability,scholar},
mendeley-tags = {alm,framework,hypermodel,interoperability,scholar},
title = {innovative interoperability framework for enterprise applications within virtual enterprises},
url = {http://portal.acm.org/citation.cfm?id=1643884},
year = {2009}
}
@misc{Janak,
annote = {Art\'{\i}culo que contiene informaci\'{o}n general de las fases recogidas en las etiquetas y que luego analiza una serie de herramientas que puede ser utilizadas para esas fases confront\'{a}ndolas con las tareas que se deben hacer en cada una de ellas.
      },
author = {Janak, J.},
file = {::},
keywords = {configuration,evaluation,general,management,requirements,tools},
mendeley-tags = {configuration,evaluation,general,management,requirements,tools},
title = {{Issue Tracking Systems}},
url = {http://74.125.155.132/scholar?q=cache:sypbS\_C6-XkJ:scholar.google.com/\&hl=es\&as\_sdt=2000}
}
@misc{Margaria2005,
abstract = {We present jETI, a redesign of the Electronic Tools Integration platform (ETI), that addresses the major issues and concerns accumulated over seven years of experience with tool providers, tool users and students. Most important was here the reduction of the effort for integrating and updating tools. jETI combines Eclipse with Web Services functionality in order to provide (1) lightweight remote component (tool) integration, (2) distributed component (tool) libraries, (3) a graphical coordination environment, and (4) a distributed execution environment. These features will be illustrated in the course of building and executing remote heterogeneous tool sequences.},
annote = {Art\'{\i}culo breve que presenta una arquitectura para la integraci\'{o}n de funcionalidades de distintas herramientas en una sola basada en eclipse y en los est\'{a}ndares de servicios Web.
Basada en Java y propone una arquitectura para ello.

      },
author = {Margaria, Tiziana and Nagel, Ralf and Steffen, Bernhard},
booktitle = {Tools and Algorithms for the Construction and Analysis of Systems},
doi = {10.1007/978-3-540-31980-1\_38},
isbn = {978-3-540-25333-4},
keywords = {architecture,eclipse,integration,services,tool},
mendeley-tags = {architecture,eclipse,integration,services,tool},
pages = {557--562},
publisher = {Springer Berlin / Heidelberg},
title = {{jETI: A Tool for Remote Tool Integration}},
url = {http://www.springerlink.com/content/h9x6m1x21g5lknkx},
volume = {3440/2005},
year = {2005}
}
@article{Ragan2006,
abstract = {Achieving developer acceptance of standardized procedures for managing applications
  from development to release is one of the largest hurdles facing organizations
  today. Establishing a standardized development-to-release workflow, often referred
  to as the ALM (application lifecycle management) process, is particularly critical
  for organizations in their efforts to meet tough IT compliance mandates. This
  is much easier said than done, as different development teams have created
  their own unique procedures that are undocumented, unclear, and nontraceable.},
annote = {Breve art\'{\i}culo que habla sobre como llegar a implante un proceso ALM dentro de una organizaci\'{o}n donde los desarrolladores no siempre lo ven bien. Habla de las principales \'{a}reas del proceso ALM en las que participa el desarrollador que son:

        
- SCM
-Build Configuration Management.

        
De hecho enuncia que para el proceso ALM lo que internamente hagan los desarrolladores debe dar igual. Lo que s\'{\i} se debe hacer es que los desarrolladores sigan algunos est\'{a}ndares para conseguir esa conformidad o aceptaci\'{o}n (COMPLIANCE)},
author = {Ragan, Tracy},
journal = {Queue},
keywords = {Compliance,alm,application,lifecycle,management},
mendeley-tags = {Compliance,alm,application,lifecycle,management},
number = {7},
title = {{Keeping Score in the IT Compliance Game}},
url = {http://portal.acm.org/citation.cfm?id=1160434.1160450},
volume = {4},
year = {2006}
}
@article{BRERETON2007,
abstract = {A consequence of the growing number of empirical studies in software engineering is the need to adopt systematic approaches to assessing and aggregating research outcomes in order to provide a balanced and objective summary of research evidence for a particular topic. The paper reports experiences with applying one such approach, the practice of systematic literature review, to the published studies relevant to topics within the software engineering domain. The systematic literature review process is summarised, a number of reviews being undertaken by the authors and others are described and some lessons about the applicability of this practice to software engineering are extracted. The basic systematic literature review process seems appropriate to software engineering and the preparation and validation of a review protocol in advance of a review activity is especially valuable. The paper highlights areas where some adaptation of the process to accommodate the domain-specific characteristics of software engineering is needed as well as areas where improvements to current software engineering infrastructure and practices would enhance its applicability. In particular, infrastructure support provided by software engineering indexing databases is inadequate. Also, the quality of abstracts is poor; it is usually not possible to judge the relevance of a study from a review of the abstract alone.},
annote = {El abstract de este art\'{\i}culo me puede servir para motivar el apartado de estudios relacionados de la tesis
        
Recoge muy bien las fases de la SLR y las justifica utiliz\'{a}ndo tambi\'{e}n una serie de casos de estudio.
        
Lo m\'{a}s importante es la construcci\'{o}n de la cadena de b\'{u}squeda aunque puede ser redefinida (habr\'{a} que justificarlo)
        
Las revisiones deben ser validadas por varios de acuerdo a un protocolo.
        
Debo de tener un glosario de t\'{e}rminos
        
Me cita las fuente s y debo indicar las peculiaridades de todos los buscadores.
        
Debo de llevar a cabo tb un protocolo de extracci\'{o}n de datos
        
Debo registrar todas las decisiones que lleve a cabo durante la SLR
      },
author = {BRERETON, P and KITCHENHAM, B and BUDGEN, D and TURNER, M and KHALIL, M},
journal = {Journal of Systems and Software},
keywords = {SLR},
mendeley-tags = {SLR},
month = apr,
number = {4},
pages = {571--583},
title = {{Lessons from applying the systematic literature review process within the software engineering domain}},
url = {http://dx.doi.org/10.1016/j.jss.2006.07.009},
volume = {80},
year = {2007}
}
@inproceedings{Lopes2007,
address = {Munich},
annote = {Art\'{\i}culo que afronta los problemas del trabajo colaborativo sobre modelos (concretamente sobre modelos UML)

        
Propugna una propagaci\'{o}n autom\'{a}tica del cambio lo que seg\'{u}n el art\'{\i}culo mejora todas las herramientas.

      },
author = {Lopes, M. and Werner, C. and Mangan, M.},
booktitle = {Proceedings for International Workshop TOMAG+REMIDI},
file = {::},
keywords = {change,propagation,tool,traceability},
mendeley-tags = {change,propagation,tool,traceability},
pages = {12--21},
publisher = {Center for Telematics and Information Technology (CTIT)},
title = {{MAIS: an awareness mechanism for change identification on shared models}},
year = {2007}
}
@article{Becker2004,
annote = {S\'{\i}ComContiene una serie de conceptos generales que puedes ser muy \'{u}tiles para la integraci\'{o}n de herramientas. 

        
Habla de la composici\'{o}n de herramientas utlizando funcionalidades de otras que viene a ser un poco la idea general que tenemos de componer distintos plugins de eclipse.

        
Para ello propone una aproximaci\'{o}n incremental y un arquitectura de integraci\'{o}n basada en un INtegrato CORE.

        
Todo ello lo engloba en un proceso que consta de los siguimientes pasos.

        
-Definici\'{o}n del modelo de arquiectura.
- Contrucci\'{o}n y modelado de los wrappers (que son los elementos que nos van a permitir las distintas herramientas)
-MOdelos ejecutables.

        
Y para cada uno de los pasos propone una serie de metamodelos .

        
Puede ser interesante la bibliograf\'{\i}a que contiene.

      },
author = {Becker, Simon M. and Haase, Thomas and Westfechtel, Bernhard},
doi = {10.1007/s10270-004-0071-0},
issn = {1619-1366},
journal = {Software \& Systems Modeling},
keywords = {architecture,integration,model,tool,wrappers},
mendeley-tags = {architecture,integration,model,tool,wrappers},
month = nov,
number = {2},
pages = {123--140},
title = {{Model-based a-posteriori integration of engineering tools for incremental development processes}},
url = {http://www.springerlink.com/index/10.1007/s10270-004-0071-0},
volume = {4},
year = {2004}
}
@misc{Kuipers,
abstract = {Outsourcing application development or maintenance, especially offshore, creates a greater need for hard facts to manage by. We have developed a tool-based method for software monitoring which has been deployed over the past few years in a diverse set of outsourcing situations. In this paper we outline the method and underlying tools, and through several case reports we recount our experience with their application. I.},
annote = {No tiene mucho que ver. Lo \'{u}nico es que proporiciona una metodolog\'{\i}a y una serie de pr\'{a}cticas de calidad que se basan en la norma ISO/IEC 9126

        
Pretende solucionar los problemas de outsourcing con herramientas de monitorizaci\'{o}n.

        

        

        

      },
author = {Kuipers, Tobias},
file = {::},
keywords = {outsourcing,quality},
mendeley-tags = {outsourcing,quality},
title = {{Monitoring the Quality of Outsourced Software}},
url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.96.2500}
}
@book{Han2009,
abstract = {The application of workflow scheduling in managing individual actor’s personal worklist is one area that can bring great improvement
  to business process. However, current deterministic work cannot adapt to the dynamics and uncertainties in the management
  of personal worklist. For such an issue, this paper proposes a two-stage probabilistic approach which aims at assisting actors
  to flexibly manage their personal worklists. To be specific, the approach analyzes every activity instance’s continuous probability
  of satisfying deadline at the first stage. Based on this stochastic analysis result, at the second stage, an innovative scheduling
  strategy is proposed to minimize the overall deadline violation cost for an actor’s personal worklist. Simultaneously, the
  strategy recommends the actor a feasible worklist of activity instances which meet the required bottom line of successful
  execution. The effectiveness of our approach is evaluated in a real-world workflow management system and with large scale
  simulation experiments.},
address = {Berlin, Heidelberg},
annote = {Art\'{\i}culo interesante. Puede servir de base para gestionar la asignaci\'{o}n de tareas y diminuir el incumplimiento de plazos.

        
Contiene tambi\'{e}n referencias buenas sobre workflow scheduling

        
Presenta a su vez dos conceptos importantes:
-Feasible work
-infeasible work

        
Propone una lista din\'{a}mica de tareas para los usuarios basadas en Redes de Petri y un modelo matem\'{a}tico que lo sustenta

      },
author = {Han, Rui and Liu, Yingbo and Wen, Lijie and Wang, Jianmin},
booktitle = {On the Move to Meaningful Internet Systems: OTM 2009},
editor = {Meersman, Robert and Dillon, Tharam and Herrero, Pilar},
keywords = {management,scheduling,task},
mendeley-tags = {management,scheduling,task},
pages = {24--41},
publisher = {Springer Berlin Heidelberg},
series = {Lecture Notes in Computer Science},
title = {{On the Move to Meaningful Internet Systems: OTM 2009}},
url = {http://www.springerlink.com/content/jv040201012m4758},
volume = {5870},
year = {2009}
}
@book{Kaariainen2009,
abstract = {Development and verification of complex systems requires close collaboration between different disciplines and specialists
  operating in a global development environment with various tools and product data storage. Fluent integration of the tools
  and databases facilitate a productive development environment by enabling the user to easily launch tools and transfer information
  between the disconnected databases and tools. The concept of Application Lifecycle Management (ALM) was established to indicate
  the coordination of activities and the management of artefacts during the software product’s lifecycle. This paper presents
  the analysis of an open source global tool integration environment called ToolChain, and proposes improvement ideas for it
  towards application lifecycle management. The demonstration of ToolChain and the collection of improvement proposals were
  carried out in the telecommunication industry. The analysis was made using the ALM framework and Global Software Development
  (GSD) patterns developed in previous studies in the automation industry.},
address = {Berlin, Heidelberg},
annote = {Establece el concepto de ALM como la coordinaci\'{o}n de actividades y gesti\'{o}n de artifacts.

        
Propone una herramienta Tool Chain que deber\'{\i}a bajar y cuyo objetivo es proporcionar un marco global para trazabilidad y visibilidad de los datos del proyecto con diferentes tipos de herramientas.

        
Propone una arquitetura de componentes que viene a ser m\'{a}s o menos lo que nosotros tenemos en mente.

        
Tiene una referencia muy importante "el uso de difentes herramientas no debe introducir nueva complejidad en el proceso de desarrollo y la informaci\'{o}n debe ser disponible de una manera sencilla.
OTM 2009 Workshop.

        
Es muy parecido a los que buscamos nosotros pero no habla nada de servicios... habr\'{\i}a que ver como consigue esa integraci\'{o}n.

      },
author = {K\"{a}\"{a}ri\"{a}inen, Jukka and Eskeli, Juho and Teppola, Susanna and V\"{a}lim\"{a}ki, Antti and Tuuttila, Pekka and Piippola, Markus},
booktitle = {On the Move to Meaningful Internet Systems: OTM 2009 Workshops},
editor = {Meersman, Robert and Herrero, Pilar and Dillon, Tharam},
keywords = {alm,architecture,integration,lifecycle,tool},
mendeley-tags = {alm,architecture,integration,lifecycle,tool},
pages = {238--247},
publisher = {Springer Berlin Heidelberg},
series = {Lecture Notes in Computer Science},
title = {{On the Move to Meaningful Internet Systems: OTM 2009 Workshops}},
url = {http://www.springerlink.com/content/r285p4675535ku2p},
volume = {5872},
year = {2009}
}
@misc{YoungC.;VelurS.K.;ChaseR.;GuckR.L.;AmbichlE.;2010,
annote = {La patente que parece cubrir el trabajo de Borland OpenALM

        
Presenta una arquitectura de referencia bastante parecida a la que pretendemos pero puede ser que no tenga un motor de workflow (aunque no est\'{a} muy claro ya que la terminolog\'{\i}a que utiliza es extra\~{n}a).

        
Habr\'{\i}a que releer la descripci\'{o}n detallada de la patente si nos interesa. (aunque es un rollaco)

        

        

        

      },
author = {{Young C.; Velur S.K.; Chase R.; Guck R.L.; Ambichl E.;} and {Sauers R.D.; Gronback R.C.}},
keywords = {alm,architecture,framework,patent},
mendeley-tags = {alm,architecture,framework,patent},
title = {{Open Application LifeCycle Management Framework}},
year = {2010}
}
@book{Hellerstein2008,
abstract = {Application lifecycle management (ALM) provides a wholistic approach to software products, from product requirements through operations. The advent of software product lines (SPLs) such as Microsoftpsilas Visual Studio creates challenges for ALM since product codes are combined in various ways to produce different customer releases or SKUs. This paper proposes an approach to making packaging decisions for SPLs. We begin by showing how industry best practices for application management as described in the IT Infrastructure Library (ITIL) should be extended to include packaging. Next, we develop a cost model and several algorithms that quantify the trade-offs between vendor costs and customer costs. Ideally, we want a packaging scheme that has the smallest customer cost at a given vendor cost. Unfortunately, finding this optimal trade-off by exhaustive search has computational complexity greater than O(n22n), where n is the number of SKUs. We develop a ldquogreedyrdquo algorithm that iteratively selects SKUs to place in the same package so that the smallest packaging overheads result. This approach has complexity O(n4). Our studies of Visual Studio SKUs show that the trade-offs produced by the greedy algorithm converge rapidly to the optimal trade-offs as we increase the number of packages in a packaging scheme.},
annote = {Art\'{\i}culo que se centra en la fase de empaquetado de productos de SPL y que como parte interesante nos muestra las partes de ITIL que se relacionan con nuestra investigaci\'{o}n que son:

        
- Application Management
- Service Support},
author = {Hellerstein, J.L.},
booktitle = {NOMS 2008 - 2008 IEEE Network Operations and Management Symposium},
keywords = {ALM,SPL,application,lifecycle,management,packaging},
mendeley-tags = {ALM,SPL,application,lifecycle,management,packaging},
pages = {1--8},
publisher = {IEEE},
title = {{Optimizing software packages for application management}},
url = {http://ieeexplore.ieee.org/lpdocs/epic03/wrapper.htm?arnumber=4575110},
year = {2008}
}
@article{Maham2008,
abstract = {One of the fundamental principles in Agile methods is to have feedback loops so that the team and organization can be learning and improving their approach to accomplishing goals. As a Scrum Master, I found lots of resources on short feedback loops from pairing, automated tests and builds and iteration retrospectives. For a higher level retrospective, one spanning an entire release, I put together an agenda from scratch. This report captures how I put together and conducted the retrospective and lessons learned from that process.},
annote = {Art\'{\i}culo corto relacionado con OpenALM. Habla de recoger datos de aplicaciones de terceros para ser integrado en interaciones \'{a}giles. La recogida ser\'{\i}a en un datawarehouse.

        
Y desde el punto de vista de la plnificaci\'{o}n de la lanzamientos (release)

      },
author = {Maham, Michael},
journal = {AGILE},
keywords = {agile,alm,borland,datwarehouse,planning,release},
mendeley-tags = {agile,alm,borland,datwarehouse,planning,release},
title = {{Planning and Facilitating Release Retrospectives}},
url = {http://portal.acm.org/citation.cfm?id=1443221.1443490},
year = {2008}
}
@misc{Kitchengam2004,
annote = {undefined},
author = {Kitchengam},
file = {::},
institution = {Keele University},
keywords = {SLR},
mendeley-tags = {SLR},
title = {{Procedures for Performing Systematic Reviews}},
url = {http://74.125.155.132/scholar?q=cache:BcjLguc5PKYJ:scholar.google.com/\&hl=es\&as\_sdt=2000},
year = {2004}
}
@book{Dumas2005,
author = {Dumas, Marlon and van der Aalst, Wil and {Ter Hofstede}, Arthur},
isbn = {0471663069},
keywords = {previo},
mendeley-tags = {previo},
title = {{Process Aware Information Systems: Bridging People and Software Through Process Technology}},
year = {2005}
}
@misc{Henderson-Sellers2002,
abstract = {Deriving a unique software development process is not possible since the requirements of individual projects vary significantly. What is possible is a standard framework, defined by a metamodel, which can then provide an extensible and tailorable process environment such that individual and project-specific processes can be created and configured precisely to those project needs. As an illustration of this approach, the OPEN Process Framework (OPF) is described in terms of its underpinning metamodel. The use of this framework to construct individual process instances is then described, first in principle and then illustrated by three case studies: a process for mid-sized MIS development; a process for Web development; and a process to assist organizations in transitioning from a non-OO to an OO development culture.},
annote = {Articulo algo antiguo que contiene un mont\'{o}n de definiciones sobre procesos, ciclo de vida y los elementos que lo componen.

        
Tiene una lista de "impacto" de implantaci\'{o}n de una metodolog\'{\i}a

        
Tiene una afirmaci\'{o}n que dice que no es posible un proceso para todos y habla del tailoring.

        
Es el primero que habla de versiones.

        
Habla de t\'{e}cnica como apoyo a la tarea (el how)

        
Y lo m\'{a}s interesante, afirma que los diagramas de procesos no llevan asociado scheduling y da una soluci\'{o}n mediante una de las clases del metamodelo que proponen

        

        

      },
author = {Henderson-Sellers, Brian},
booktitle = {Annals of Software Engineering},
keywords = {concepts,example,general,metamodel,methodology,process},
mendeley-tags = {concepts,example,general,metamodel,methodology,process},
number = {1},
pages = {341--362--362},
publisher = {Springer Netherlands},
title = {{Process Metamodelling and Process Construction: Examples Using the OPEN Process Framework (OPF)}},
url = {http://www.springerlink.com/content/h89002x566217606/},
volume = {14},
year = {2002}
}
@article{Gruhn2002,
annote = {Habla de que los diferentes tipos de procesos necesitar\'{a}n diferentes tipos de herramientas.

        
Dice que los PCSEE llevan el concepto de modelo predefinido de proceso.

        

        
Este modelo debe ser flexible pero no puede ser del todo flexible. (compromiso)

        
Enlaza tambi\'{e}n con el concepto de intregaci\'{o}n ya que ferentes tipos de partes del proceso  necesitar\'{a}n diferentes tipos de herramientas.

        
Y habla de los diferentes tipos de autonom\'{\i}a.

        

      },
author = {Gruhn, V},
journal = {Annals of Software Engineering},
keywords = {PCSEE,process},
mendeley-tags = {PCSEE,process},
number = {1-4},
pages = {363 -- 382},
title = {{Process--Centered Software Engineering Environments, A Brief History and Future Challenges}},
volume = {14},
year = {2002}
}
@article{Bradbury2008,
abstract = {This is not going to be pretty. You're in charge of a software development team, your two-year project was delivered over budget and over deadline - and the users are complaining that it doesn't do what they want. Simply using an integrated development environment (IDE) isn't enough to produce robust software these days. Application lifecycle management (ALM) is a category of software designed to manage all aspects of a software application's production, giving earnest developers the chance to answer those questions, or better still, avoid them coming up at all.},
annote = {/Muy breve art\'{\i}culo que como cosa interesante:

        
-La met\'{a}fora ALM-IDE Word-CMS
- Cita algunos fabricantes y los defectos de Borland},
author = {Bradbury, D.},
journal = {Engineering \& Technology},
keywords = {alm,alm application lifecycle management,application,lifecycle,management},
mendeley-tags = {alm,application,lifecycle,management},
number = {21},
pages = {55 -- 56},
title = {{Processes with a point - [IT software]}},
url = {http://ieeexplore.ieee.org/xpl/freeabs\_all.jsp?arnumber=4805176},
volume = {3},
year = {2008}
}
@article{Heimbigner1990,
annote = {Art\'{\i}culo cl\'{a}sico pero que contiene unos conceptos muy claros.

        
Contiene las definiciones de prescriptivos y proscriptivo y las ventajas e inconvenientes de cada uno de ellos.

        
Uno de los puntos m\'{a}s importantes es lo que sale en la p\'{a}gina 3, en la que apoyado en Osterweil abogo por un uso mixto de los dos enfoques.

        

      },
author = {Heimbigner, D},
keywords = {prescriptive,process,proscriptive},
mendeley-tags = {prescriptive,process,proscriptive},
pages = {99 -- 102},
title = {{Proscription versus Prescription in Process--Centered Environments}},
year = {1990}
}
@phdthesis{AndreaCasarella2008,
annote = {No tiene mucho que ver salvo que lo interesante es el overview que hace de c\'{o}mo hacer un plugin para Eclipse

      },
author = {{Andrea Casarella}},
file = {::},
keywords = {eclipse,metrics,plug-in,quality},
mendeley-tags = {eclipse,metrics,plug-in,quality},
pages = {48},
school = {Universit\'{a} della Svizzera italiana},
title = {{Proximity Alert: An Eclpise Plug-in for Software Analysis}},
year = {2008}
}
@article{Umar2009,
author = {Umar, Amjad and Zordan, Adalberto},
doi = {10.1016/j.jss.2008.07.047},
issn = {01641212},
journal = {Journal of Systems and Software},
keywords = {previo},
mendeley-tags = {previo},
number = {3},
pages = {448--462},
title = {{Reengineering for service oriented architectures: A strategic decision model for integration versus migration}},
url = {http://linkinghub.elsevier.com/retrieve/pii/S0164121208001842},
volume = {82},
year = {2009}
}
@inproceedings{Heindl2007,
address = {Munich},
annote = { Tiene varias cosas muy interesantes.

        
Se centra en desarrollos llevados a cabo por equipos distribuidos donde existe la posibilidad de que haya varios miembros trabajando a la vez.

        
Cita una serie de herramientas t\'{\i}picas REQM tool, IDE, SCM, TESTMNG, y plataformas de colaboraci\'{o}n y comunicaci\'{o}n.

        
Personalmente creo que aunque los equipos no sean distribuidos es importante incluir este tipo de herramientas en los entornos ALM sobre los que estamos investigando.

        

        
Para este tipo de entornos distribuidos propone el concepto "Requirements awareness mechnism" y propone una serie de caracter\'{\i}sticas  que deben tener los proyectos de este tipo GDS 
en su empresa (Siemens)

        
-"Requirements awareness mechnism" Es decir un intercambio de informaci\'{o}n efectiva.
-Trazabilidad de requisitos
-Integraci\'{o}n de herramientas aunque este es el mayor problema, la integraci\'{o}n entre las herramientas de desarrollo y las de requisitos.

        

        
Para solucionar esto lo soluciona con un sistema de notificaci\'{o}n orientado en roles. Se notifica de los cambios a todo el mundo relacionado.

        
La pregunta es si este tipo de enfoque se pueden modelar y dispararse con eventos. (con BPMN)

        
Propone una lista de eventos que habr\'{\i}a que manejar para este tipo de entornos. Basado en reglas (¿drools?)

        
Propone una arquitectura de este Role-Oriented Notification System que es importante tener en cuenta. En realidad tiene una estructura visual muy parecida al esquema ALM de Schawber.

        

        
Habla de un formato de intercambios de datos \'{u}nico para todo el proceso?

        

      },
author = {Heindl, M. and Reinisch, F. and Biffl, S.},
booktitle = {Proceedings for International Workshop on TOMAG+REMIDI },
keywords = {Awareness,Event,GSD,Notification,Requirements,Role},
mendeley-tags = {Awareness,Event,GSD,Notification,Requirements,Role},
pages = {46--52},
publisher = {Center for Telematics and Information Technology (CTIT)},
title = {{Requirements Management Infraestructures in Global Software Development - Towards Application LifeCycle Management with Role-Oriented In-Time Notification}},
year = {2007}
}
@misc{GobleG.2008,
annote = {Habla de utilizar la sem\'{a}ntica a la hora de descubir servicios y no el m\'{e}todo prueba y error.
Presenta un mont\'{o}n de est\'{a}ndares relacionados con la sem\'{a}ntica y los servicios (RDF por ejemplo)
Ser\'{\i}a un paso m\'{a}s avanzado de la investigaci\'{o}n ya que nosotros los servicios los elegiremos al configurar el entorno de trabajo.

      },
author = {{Goble G.} and {Kuo D.} and {Parastatidis S.} and {Watson P.}},
file = {::},
institution = {University of Manchester; University of Newcastle},
keywords = {integration,semantic,services},
mendeley-tags = {integration,semantic,services},
publisher = {Scientific Commons},
title = {{Scientific Commons: Building Large-scale, Service-Oriented Distributed Systems using Semantic Models (2008), 2008-08-14 [Carole Goble, Dean Kuo, Savas Parastatidis, Paul Watson]}},
url = {http://en.scientificcommons.org/42394691},
year = {2008}
}
@misc{Eskeli2009,
abstract = {VTT Publications 725. This thesis presents how the hardware-related software development process can be improved by means of tool integration. Challenges in hardware-related software development are diverse, which is why a multitude of tools is needed during the development. The tools produce data that needs to be managed, but the tools are disconnected. Tool integration provides a means of bringing the data from disconnected tools together into one coherent, easily manageable package. Research was conducted by initially perceiving hardware-related software development from a systems engineering viewpoint, with a focus on several well-known process models. This was done to understand the kinds of activities that need to be supported by the tools. A workflow concept was introduced as a means to support the development effort of an individual worker. An extensive background study into tool integrations was conducted to understand state-of-the-art tool integration approaches and concepts, and then used to create the foundation for the tool integration. Hardware-related software development challenges were gathered from literature and industry experiences to reinforce the understanding on needed tool support and to specify the requirements for the tool integration. The main requirements for the tool integration were easy extensibility, which could only be provided via a framework-based solution, and a means to provide data flow from tool to tool while preserving traceability between the data from the tools. Tool requirements for the integration were project management, requirement management, test management, and change management tools. Emphasis was put on tools supporting testing and test analysis. The tool integration, ToolChain, was implemented in two phases. In the first phase the groundwork for the integration framework was done. Eclipse was chosen as the platform for the integration and plug-ins selected as a means of implementation. In the second phase, tool support focusing on the hardware-related software development aspects was added. Implementations from each phase were validated separately in industry cases. Experiences from these cases are presented in which it is shown how ToolChain can be easily adapted into the target company's environments, and how the tool integration improves the way of working.. This thesis presents how the hardware-related software development process can be improved by means of tool integration. Challenges in hardware-related software development are diverse, which is why a multitude of tools is needed during the development. The tools produce data that needs to be managed, but the tools are disconnected. Tool integration provides a means of bringing the data from disconnected tools together into one coherent, easily manageable package. Research was conducted by initially perceiving hardware-related software development from a systems engineering viewpoint, with a focus on several well-known process models. This was done to understand the kinds of activities that need to be supported by the tools. A workflow concept was introduced as a means to support the development effort of an individual worker. An extensive background study into tool integrations was conducted to understand state-of-the-art tool integration approaches and concepts, and then used to create the foundation for the tool integration. Hardware-related software development challenges were gathered from literature and industry experiences to reinforce the understanding on needed tool support and to specify the requirements for the tool integration. The main requirements for the tool integration were easy extensibility, which could only be provided via a framework-based solution, and a means to provide data flow from tool to tool while preserving traceability between the data from the tools. Tool requirements for the integration were project management, requirement management, test management, and change management tools. Emphasis was put on tools supporting testing and test analysis. The tool integration, ToolChain, was implemented in two phases. In the first phase the groundwork for the integration framework was done. Eclipse was chosen as the platform for the integration and plug-ins selected as a means of implementation. In the second phase, tool support focusing on the hardware-related software development aspects was added. Implementations from each phase were validated separately in industry cases. Experiences from these cases are presented in which it is shown how ToolChain can be easily adapted into the target company's environments, and how the tool integration improves the way of working. },
address = {Vuorimiehentie},
annote = {Art\'{\i}culo muy interesante por el planteamiento de base porque es muy parecido a lo que pretendemos aunque en ning\'{u}n momento hace referencia a los servicios como tecnolog\'{\i}a base para la integraci\'{o}n.

        
Se centro en un tipo de software que tiene poco que ver con el software en el que nos vamos a centrar.

        
Identifica muy claramente los problemas de la tool-integration aunque en la p\'{a}gina 17 hace una afirmaci\'{o}n muy interesante "No parece existir una forma correcta de conseguir esta tool integration"

        
Dice que est\'{a} TOOL INTEGRATION es un objetvio europeo (pg18)

        
Habla de los niveles de integraci\'{o}n y de los diferentes enfoques que existen.

        
Habla de la TOOL INTEGRATION desde el punto de vista de ALM y cita los elementos que debe tener este enfoque (pg 21) Coinciden con los de Schaweber.

        
Tiene una lista de implementaciones de ALM (pg229 que habr\'{\i}a que revisar)

        
Enmarca todo ello y lo afronta con la herramienta ToolChain y presenta una arquitectura o esquema para esta herramienta y explica c\'{o}mo la ha desarrollado bas\'{a}ndose en esa arquitectura y en Eclipse como marco de desarrollo.

      },
author = {Eskeli, J.},
file = {::},
institution = {VTT Technical Researcn Center of Finland },
isbn = {978-951-38-7373-8},
issn = {1455-0849},
keywords = {Architecture,Europe,ToolChain,alm,development tools,eclipse,integration,objective,plug-in,tool,tool integration},
mendeley-tags = {Architecture,Europe,ToolChain,alm,eclipse,integration,objective,plug-in,tool},
publisher = {VTT },
title = {{Scientific Commons: Integrated tool support for hardware related software development (2009), 2009 [Eskeli, Juho]}},
url = {http://www.vtt.fi/inf/pdf/publications/2009/P725.pdf},
year = {2009}
}
@misc{,
annote = {Art\'{\i}culo de compa\~{n}ia que se centra en hacer que el cambio en el desarrollo de software sea el centro de todo.

        
Repasa un poco de cultura general al respecto (definici\'{o}n, enfoques para afrontar el cambio) y luego presenta la herramienta que la compa\~{n}ia tiene para ello.

        
Cita siempre CMMI e ITIL (siempre suelen estar presentes en la gesti\'{o}n del ciclo de vida).

        
Lo pque pretende conseguir con su colecci\'{o}n de herramientas comerciales es:
- Visualizar el impacto de los cambios como motro del ciclo de vida que es
-Orquestar la toma de requisitos y el desarrollo (los procesos de..)
-Unifcar los procesos

        
las herramientas no son opensource ni son gratuitas aunque de algunas se puede conseguir versi\'{o}n de evaluaci\'{o}n. desde luego no parece que est\'{e}n abiertas a la integraci\'{o}n de nuevas herramientas de terceros que es algo fundamental que pretendemos.

      },
file = {:home/pekechis/.local/share/data/Mendeley Ltd./Mendeley Desktop/Downloaded/Unknown - Unknown - Serena Change governanCe SolutionS(2).html:html},
institution = {Serena},
keywords = {ALM,change,comercial,lifecycle,management},
mendeley-tags = {ALM,change,comercial,lifecycle,management},
title = {{Serena Change governanCe SolutionS}}
}
@misc{Case2007,
annote = {No aporta mucho salvo una lista de est\'{a}ndares  (pg43) y dos conceptos como el KPI y el KGI (Key Goal Indicator)

      },
author = {Case, G. and DuMoulin, T. and Spalding, G. and Dissanayake, A.C.},
editor = {Wilkinson, J.},
file = {::},
keywords = {management,services},
mendeley-tags = {management,services},
pages = {37--50},
publisher = {Van Haren Publishing},
title = {{Service Management Strategies that work: Guidance for executives}},
year = {2007}
}
@article{Tsai2007,
abstract = {Abstract\&nbsp;\&nbsp;In the past few years, we witnessed a rapid progress in service-oriented computing (SOC), which represents a new computing
  paradigm. SOC changes the way we develop and use software and hardware. Major enabling techniques, including service-oriented
  architecture (SOA), service-oriented enterprise (SOE), service-oriented infrastructure (SOI), Web services (WS), and associated
  protocols and standards are being established. This paper focuses on the system engineering issues and how these engineering
  issues manifested in SOA development processes. SOSE differs from traditional system engineering because it emphasizes on
  reusability, dynamic and adaptive nature, and unique model-driven approach.},
annote = {Art\'{\i}culo centrado en Servicios y en el enfoque IBM SOA (con varias referencias sobre esto que parecen interesantes)
Introduce nuevos t\'{e}rminos como:

        
- SOSE. Service Oriented System Engineering
- CCSOA Consumer Centric SOA
- SMMA Single Model Multiple Analysis

        
Se centra en el desarrollo de sistemas empotrados y tiene en cuenta el aspecto colaborativo del desarrollo de sistemas SOA

        

      },
author = {Tsai, Wei-Tek and Wei, Xiao and Paul, Ray and Chung, Jen-Yao and Huang, Qian and Chen, Yinong},
journal = {Service Oriented Computing and Applications},
keywords = {Collaboration,Data,Dynamic,Provenance,SOSE,Service},
mendeley-tags = {Collaboration,Data,Dynamic,Provenance,SOSE,Service},
month = apr,
number = {1},
pages = {3--17},
title = {{Service-oriented system engineering (SOSE) and its applications to embedded system development}},
url = {http://www.springerlink.com/index/10.1007/s11761-007-0003-2},
volume = {1},
year = {2007}
}
@book{Sarang2007,
author = {Sarang, Poornachandra},
isbn = {1904811175},
keywords = {ESB,SOA,services},
mendeley-tags = {ESB,SOA,services},
title = {{SOA Approach to Integration: XML, Web services, ESB, and BPEL in real-world SOA projects}},
year = {2007}
}
@misc{Liu,
annote = {Cultura general sobre estas dos fases y compartiva de distintas herramientas de este tipo.

        

      },
author = {Liu, Sha},
file = {::},
keywords = {change,configuration,integration,management,software},
mendeley-tags = {change,configuration,integration,management,software},
title = {{Software Condiguration and Change Management}},
url = {http://74.125.155.132/scholar?q=cache:388zDzA6AKIJ:scholar.google.com/\&hl=es\&as\_sdt=2000}
}
@article{Dearle2007,
abstract = {This paper examines the dimensions influencing the past and present and speculates on the future of software deployment. Software deployment is a postproduction activity that is performed for or by the customer of a piece of software. Today's software often consists of a large number of components each offering and requiring services of other components. Such components are often deployed into distributed, heterogeneous environments adding to the complexity of software deployment. This paper sets out a standard terminology for the various deployment activities and the entities over which they operate. Six case studies of current deployment technologies are made to illustrate various approaches to the deployment problems. The paper then examines specific deployment issues in more detail before examining some of the future directions in which the field of deployment might take.},
annote = {Art\'{\i}culo que se centra exclusivamente en la fase de deploy y que hace un recorrido sobre la terminolog\'{\i}a y los retos en esta fase. Afirma quye la virtualizaci\'{o}n puede ser un buen enfoque para resolver muchos de esos problemas. En relaci\'{o}n a ALM s\'{o}lo destacar que s\'{\i} que recoge una afirmaci\'{o}n que muestra la importancia de la trazabilidad de los distintos artifacts a lo largo de todo el ciclo de vida},
author = {Dearle, Alan},
journal = {International Conference on Software Engineering},
keywords = {deployment},
mendeley-tags = {deployment},
pages = {15},
title = {{Software Deployment, Past, Present and Future}},
url = {http://portal.acm.org/citation.cfm?id=1253532.1254724},
year = {2007}
}
@article{Ossher2000,
annote = {art\'{\i}culo que hace una revisi\'{o}n hist\'{o}rica de las herramientas y los entornos de ingenier\'{\i}a del software.

        
Afirma en la p\'{a}gina 265 que el reto m\'{a}s importante en este campo en la INTEGRACI\'{O}N debido a la diversidad de los contextos de cada una de las herramientas.

        

        
Para dar soluci\'{o}n a ello introduce el concepto de software morfog\'{e}nico y para ello se basa en tecnolog\'{\i}as que no son las m\'{a}s actuales (el art\'{\i}culo es del a\~{n}o 2000) XML, EJB y Message Brokers.

        

        

        

      },
author = {Ossher, H and Harrison, W and Tarr, P},
keywords = {challengees,enviroments,history,integration,process-centered enviroments,programming support enviroments,separation of concerns,software engineering environments,tools},
mendeley-tags = {challengees,enviroments,history,integration,tools},
pages = {261 -- 277},
title = {{Software Engineering Tools and Environments: a Roadmap}},
year = {2000}
}
@article{Dowson1993,
annote = {Articulo antiguo aunque tiene algunas cosillas importantes.
        
¿Qu\'{e} es lo que se pretende con la utilizaci\'{o}n de la orientaci\'{o}n a objetos?
        
-M\'{a}s efectivo.
-Mas predecible
-Mas calidad y fiabilidad.
        
Y presenta tb que es lo que se requiere para ello:
-Construir modelos
-Aseguyrarse de que el proceso es seguido
-MOnitorizar el desarrollo de los proyectos 
        
Y luego habla de aspectos como:
        
-La notacion que voy a utilizar (textual vs gr\'{a}fico)
-El nivel de detalle al que voy a llegar al describir el proceso.
-C\'{o}mo voy a definirlo (modelo)
-NEcesitar\'{e} los servicios de ejecuci\'{o}n y monitorizaci\'{o}n
      },
author = {Dowson, M},
keywords = {general,objective,process},
mendeley-tags = {general,objective,process},
pages = {54 -- 62},
title = {{Software Process Themes and Issues}},
year = {1993}
}
@article{Fuggetta2000,
annote = {es muy importante lo que dice en el apartado 2 ya que relaciona directamente el software process con el ciclo de vida que es su base aunque aporta conceptos m\'{a}s amplos.

        
Para modelar este proceso se han creado una seri de formalismos.

        
Cita varios usos para estos modelos de procesos:

        
-Comprensi\'{o}n.
-Dise\~{n}o
-Training and education
-Simulaci\'{o}n y optimizaci\'{o}n
-Process-support

        
Marca una serie de l\'{\i}neas de investigaci\'{o}n futuras (para ese a\~{n}o claro..) que b\'{a}sicamente son que los modelos deprocesos deben permitir la flexibilidad e inconsistencia y proporcionar una vista clara del proceso al desarrollador.

      },
author = {Fuggetta, A},
keywords = {process},
mendeley-tags = {process},
pages = {25 -- 34},
title = {{Software Process: a Roadmap}},
year = {2000}
}
@article{Osterweil1987,
author = {Osterweil, L},
keywords = {process},
mendeley-tags = {process},
title = {{Software Processes are Software Too}},
year = {1987}
}
@article{Osterweil1997,
annote = {Versi\'{o}n 20 a\~{n}os despu\'{e}s del famoso art\'{\i}culo de Osterweil  que aclara algunas cosas que seg\'{u}n \'{e}l han sido malinterpretados

        
Un apartado muy importante de este art\'{\i}culo es que establece paralelismos en el proceso software y el software  y qu\'{e} hemos aprendido en 20 a\~{n}os.

        
-Los modelos son buenos pero a veces no son suficiente para el proceso de software.

        

        

        

      },
author = {Osterweil, Leon J.},
journal = {International Conference on Software Engineering},
keywords = {process,software},
mendeley-tags = {process,software},
pages = {540},
title = {{Software processes are software too, revisited: an invited talk on the most influential paper of ICSE 9}},
url = {http://portal.acm.org/citation.cfm?id=253440},
year = {1997}
}
@article{Arsanjani2008,
abstract = {Service-oriented modeling and architecture (SOMA) has been used to conduct projects of varying scope in multiple industries worldwide for the past five years. We report on the usage and structure of the method used to effectively analyze, design, implement, and deploy service-oriented architecture (SOA) projects as part of a fractal model of software development. We also assert that the construct of a service and service modeling, although introduced by SOA, is a software engineering best practice for which an SOA method aids both SOA usage and adoption. In this paper we present the latest updates to this method and share some of the lessons learned. The SOMA method incorporates the key aspects of overall SOA solution design and delivery and is integrated with existing software development methods through a set of placeholders for key activity areas, forming what we call solution templates. We also present a fractal model of software development that can enable the SOMA method to evolve in an approach that goes beyond the iterative and incremental and instead leverages method components and patterns in a recursive, self-similar manner opportunistically at points of variability in the life cycle.},
annote = {Art\'{\i}culo de IBM que presenta una metodolog\'{\i}a para desarrollar proyectos orientados aservicios.

        

        
Pueder ser importante para justificar ciertos aspectos de nuestra tesis.

        

        

      },
author = {Arsanjani, A. and Ghosh, S. and Allam, A. and Abdollah, T. and Gariapathy, S. and Holley, K.},
journal = {IBM Systems Journal},
keywords = {service: methodology,soma},
mendeley-tags = {service: methodology,soma},
number = {3},
pages = {377--396},
title = {{SOMA: a method for developing service-oriented solutions}},
url = {http://portal.acm.org/citation.cfm?id=1466610.1466613},
volume = {47},
year = {2008}
}
@article{Yap2005,
abstract = {Most software engineering tools come with fixed functionality or limited plug-in extension capabilities. Building software development environments that support truly dynamic extension capabilities to incorporate a wide range of additional facilities at run-time has proved to be a very challenging task. We describe a new approach using web service components to support the dynamic discovery, integration and invocation of remote software tool facilities for JEdit, an open source Integrated Development Environment. In this approach discrete software tool functionality is encapsulated in software "toolets", accessed as remote web service-based components. These toolet services are registered and discovered, and then dynamically integrated and invoked from within the JEdit IDE as required. We describe the architecture of our approach, key design and implementation issues, and illustrate the feasibility of the approach with several prototype toolet components and results of their evaluation.},
annote = {Es un enfoque para Jedit pero supong que podr\'{\i}a trasladarse a Eclipse.

        
El concepto clave es "Toolet" que nos permite encapsular funcionalidades de herramientas para acceder a ellas a trav\'{e}s de componentes basado en servicios Web.

        
En un principio habla de los distintos enfoques de integraci\'{o}n y de los problemas que pueden surgir.

        
Empieza a hablar tambi\'{e}n de aspectos colaborativos.

        
La integraci\'{o}n que propone es din\'{a}mica aunque no s\'{e} si es eso lo que necesito yo ya que voy a saber el tipo de herramientas que voy a necesitar.

        
Hace una propuesta de arquitectura

        

      },
author = {Yap, Nelson and Chiong, Hau Chean and Grundy, John and Berrigan, Rebecca},
journal = {ASWEC Australian Software Engineering Conference},
keywords = {Integrated development enviroment,architecture,collaboration,integration: tool,services,software tool integration,web services},
mendeley-tags = {architecture,collaboration,integration: tool,services},
pages = {160--169},
title = {{Supporting Dynamic Software Tool Integration via Web Service-Based Components}},
url = {http://portal.acm.org/citation.cfm?id=1050794},
year = {2005}
}
@article{KITCHENHAM2009,
abstract = {Background In 2004 the concept of evidence-based software engineering (EBSE) was introduced at the ICSE04 conference. Aims This study assesses the impact of systematic literature reviews (SLRs) which are the recommended EBSE method for aggregating evidence. Method We used the standard systematic literature review method employing a manual search of 10 journals and 4 conference proceedings. Results Of 20 relevant studies, eight addressed research trends rather than technique evaluation. Seven SLRs addressed cost estimation. The quality of SLRs was fair with only three scoring less than 2 out of 4. Conclusions Currently, the topic areas covered by SLRs are limited. European researchers, particularly those at the Simula Laboratory appear to be the leading exponents of systematic literature reviews. The series of cost estimation SLRs demonstrate the potential value of EBSE for synthesising evidence and making it available to practitioners.},
annote = {Art\'{\i}culo que eval\'{u}a una serie de SLR en ingenier\'{\i}a del software y que no aporta mucho sobre SLR pero que puede servir como fuente de informaci\'{o}n para buscar alg\'{u}n que otro ejemplo },
author = {KITCHENHAM, B and PEARLBRERETON, O and BUDGEN, D and TURNER, M and BAILEY, J and LINKMAN, S},
journal = {Information and Software Technology},
keywords = {SLR},
mendeley-tags = {SLR},
month = jan,
number = {1},
pages = {7--15},
title = {{Systematic literature reviews in software engineering – A systematic literature review}},
url = {http://dx.doi.org/10.1016/j.infsof.2008.09.009},
volume = {51},
year = {2009}
}
@article{Ubis2008,
abstract = {Lifecycle support of a process from conception, implementation and evaluation can be enabled in a distributed cross organisational environment using Service Orientated Architectures (SOA). In the automation domain the development of such lifecycles are both vital for the competitiveness of European manufacturing and challenging due to the environments they exist in. This paper explores the main innovations needed to achieve SOA based application lifecycle management in the automation sector initially looking at a successful lifecycle implementation in the eScience community. This highlights the need for clearly defined standards architecture and ontology building methodologies for emerging SOA communities to achieve lifecycle management around clearly defined and managed metadata.},
annote = {El punto de vista principal es el punto de vista de la industria (con la inform\'{a}tica)

        
No aporta mucho aunque reafirma la necesidad de ontolog\'{\i}as para conseguir esa integraci\'{o}n  y SOA para conseguir esos objetivos.

        
Adem\'{a}s lleva una peque\~{n}a clasificaci\'{o}n de ontolog\'{\i}as que podr\'{\i}a ser \'{u}til.

        

      },
author = {Ubis, F. and Kirkham, T. and Matthews, B. and Lastra, J. L. Martinez and Harrison, R. and Herrera, V. Villase\~{n}or and Chowdrey, A.},
journal = {COMPSAC},
keywords = {SOA,industry,integration,ontology},
mendeley-tags = {SOA,industry,integration,ontology},
title = {{The Challenges along the Road to the Realisation of a Factory Automation Lifecycle}},
url = {http://portal.acm.org/citation.cfm?id=1444455.1445985},
year = {2008}
}
@article{Schwaber2006,
author = {Schwaber, C},
keywords = {2.0,alm,requisites},
mendeley-tags = {2.0,alm,requisites},
title = {{The Changing Face Of Application Life--Cycle Management}},
year = {2006}
}
@article{Weber1991,
author = {Weber, Herbert},
doi = {10.1007/BF02265066},
issn = {0925-4676},
journal = {Journal of Systems Integration},
keywords = {previo},
mendeley-tags = {previo},
number = {1},
pages = {55--79},
title = {{The integration of reusable software components}},
url = {http://www.springerlink.com/index/10.1007/BF02265066},
volume = {1},
year = {1991}
}
@article{Wasserman1990,
annote = {Art\'{\i}culo cl\'{a}sico de Wasserman que presenta el esquema de la tostadora.

        

      },
author = {Wasserman, AI},
journal = {Proceedings of the international workshop on environments on Software engineering environments},
keywords = {general,integration,toaster,tool},
mendeley-tags = {general,integration,toaster,tool},
pages = {137 -- 149},
title = {{Tool Integration in Software Engineering Environments}},
year = {1990}
}
@misc{Wicks2004,
abstract = {The aim of this paper is to identify and investigate previous research in the area of  software engineering environments, and how tools are integrated to form such a facility,  with the goal of identifying future research questions. The paper consists of an explanation  of the method used to identify papers, with each placed in a candidate category. Each of  the seven categories is examined in turn, with each paper in each category then reviewed,  with any possible arising research questions identified by the author of this paper included.},
annote = {Art\'{\i}culo que hace una revisi\'{o}n de lo que hab\'{\i}a en tool integration en 2004.

        
Es una referencia de cultura general muy importante

        
Describe la dimensiones de tool integration y c\'{o}mo podemos medirla.

        
Recoge los tipos de tool integration y los est\'{a}ndares relacionados y una serie de expriencias industriales.

        
Es muy destacado el hecho de que posee dos apartados relacionados con procesos y t\'{e}cnicas de modelado y la tool integration 

        
Tambi\'{e}n tiene una buena serie de referencias bibliogr\'{a}ficas.

        

      },
author = {Wicks, Mike},
file = {::},
keywords = {integration,slr,tool},
mendeley-tags = {integration,slr,tool},
title = {{Tool Integration in Software Engineering: The State of the Art in 2004}},
url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.59.1969},
year = {2004}
}
@misc{Wicks2006,
annote = {Revisi\'{o}n de la literatura con referencias que habr\'{a} que ir pensando en bajar

      },
author = {Wicks, M.N.},
keywords = {integration,slr,tool},
mendeley-tags = {integration,slr,tool},
title = {{Tool integration within Software Engineering Enviroments: An annotated bibliography}},
year = {2006}
}
@inproceedings{Herrera2007,
address = {Munich},
annote = {Contiene afirmaciones importat\'{\i}simas.

        
Reafirma las necesidades de integraci\'{o}n en todas las facetas de desarrollo

        
Se refiera a GDSE (Global Distributed Software Engineering)

        
Califica los requisitos en 4 para este tipo de poryectos.

        
En el enfoque tradicional el ve el problema en que nos centramos en las herramientas y no en el proceso de desarrollo lo que provoca un problema de integraci\'{o}n cuando las herramientas son de distintos fabricantes.

        

        
Actualmente hay un enfoque mucho m\'{a}s process centric y afirma las eficiencias de las herramientas sociales y colaborativas para este tipo de equipos de desarrollo de software GDSE

        
Cita EPF y RUP

        
Es muy importante el primer p\'{a}rrafo de la conclusi\'{o}n.

        

      },
author = {Herrera, M. and van Hillegersberg},
booktitle = {Proceeding for International Workshop TOMAG+REMIDI},
file = {::},
keywords = {GDSE,requirements,tool,traceability},
mendeley-tags = {GDSE,requirements,tool,traceability},
pages = {30--36},
publisher = {Center for Telematics and Information Technology, CTIT},
title = {{Tool Support for Distributed Software Development : The past - present - and future of gaps between user requirements and tool functionalities - University of Twente Publications}},
url = {http://doc.utwente.nl/60289/},
year = {2007}
}
@article{Pierce2008,
abstract = {If designing and developing optimal products, services, and information requires clarity and audience awareness, then developing ways to acquire customer input is a critical piece in the best development workflow solutions [43]. Seeking direct input from customers and learning how they use a product are the most effective methods for generating ideas for enhancements and innovations to the technical content that supports a product, as well as to the product itself [21]. Taking the steps to create opportunities for customer feedback enables direct customer input and establishes the proactive best practice of demonstrating to the customer that they are a top priority in the product development focus [34]. While there may not be a fixed agenda for an optimal customer meeting, there may, in fact, be a set of topics for discussion that comprise a set of best practices for gaining customer input for the user assistance [45]. Customer input helps provide requests for change and thus aids in managing change, raising the importance of a change and requirements management system [34, 52]. A change and requirements management system is even more critical in the context of application lifecycle management and globally distributed development [27, 49, 50, 55]. Managing relationships with customers leads to a two-way path for collaboration, both for helping customers solve their problems and for a company to enhance its products and overall success [26, 28].},
annote = {Es un art\'{\i}culo que no tiene mucho inter\'{e}s pero que sin embargo presenta en la bibliograf\'{\i}a una serie de art\'{\i}culos muy interesantes para bajar:

        
- A process maturity framework for managing distributed development
- Using a change-management approach to promote customer-centered design
-Process Models in software engineering

        

      },
author = {Pierce, Robert},
journal = {ACM Special Interest Group for Design of Communication},
keywords = {Information,change,computer documentation,customer feedback,management,software documentation,user assistance},
mendeley-tags = {change,management},
title = {{Using customer input to drive change in user assistance}},
url = {http://portal.acm.org/citation.cfm?id=1456541},
year = {2008}
}
@article{Plessis2008,
abstract = {Knowledge management has been implemented both successfully and less successfully in organisations globally. In these implementations many barriers have been encountered that made the implementations complex. Implementations in every organisation would be unique due to the unique culture and unique circumstances in that particular organisation. This article seeks to understand what barriers have already been identified in knowledge management implementations in organisations globally today. The article also seeks to understand the context of these barriers in order to understand the bigger picture within which they take place. It also looks at how these barriers are being or has been managed, and if it has not been managed, what alternatives could have been put into place to overcome these barriers to ensure a smooth knowledge management implementation.},
annote = {No tiene mucho que ver realmente con el ALM pero si que presenta ciertas ideas interesantes sobre la implantaci\'{o}n de herramientas de knowledge management en un entorno empresarial. Sobre todo ventajas y barreras. Y nos puede servir para relacionarlo con el entorno ALM, que en cierta manera tambi\'{e}n hace una gesti\'{o}n del conocimiento (en este caso de un proceso de desarrollo)},
author = {du Plessis, M.},
journal = {International Journal of Information Management},
keywords = {knowledge,management},
mendeley-tags = {knowledge,management},
number = {4},
pages = {285--292},
title = {{What bars organisations from managing knowledge successfully?}},
url = {http://linkinghub.elsevier.com/retrieve/pii/S026840120800042X},
volume = {28},
year = {2008}
}
@article{Russell2004,
author = {Russell, N and Hofstede, Ter and Edmond, D and van der Aalst, WMP},
keywords = {data,patterns,workflow},
mendeley-tags = {data,patterns,workflow},
number = {FIT--TR--2004--01},
title = {{Workflow Data Patterns}},
year = {2004}
}
@article{VanderAalst2003,
abstract = {Differences in features supported by the various contemporary commercial workflow management systems point to different insights of suitability and different levels of expressive power. The challenge, which we undertake in this paper, is to systematically address workflow requirements, from basic to complex. Many of the more complex requirements identified, recur quite frequently in the analysis phases of workflow projects, however their implementation is uncertain in current products. Requirements for workflow languages are indicated through workflow patterns. In this context, patterns address business requirements in an imperative workflow style expression, but are removed from specific workflow languages. The paper describes a number of workflow patterns addressing what we believe identify comprehensive workflow functionality. These patterns provide the basis for an in-depth comparison of a number of commercially availablework flow management systems. As such, this paper can be seen as the academic response to evaluations made by prestigious consulting companies. Typically, these evaluations hardly consider the workflow modeling language and routing capabilities, and focus more on the purely technical and commercial aspects.},
author = {van der Aalst, W.M.P. and ter Hofstede, A.H.M. and Kiepuszewski, B. and Barros, A.P.},
journal = {Distributed and Parallel Databases},
keywords = {control,patterns,workflow},
mendeley-tags = {control,patterns,workflow},
month = jul,
number = {1},
pages = {5--51},
title = {{Workflow Patterns}},
url = {http://www.springerlink.com/content/t843m4811544232p},
volume = {14},
year = {2003}
}
@article{Russell2004a,
author = {Russell, N and Hofstede, Ter and Edmond, D and van der Aalst, WMP},
keywords = {patterns,resource,workflow},
mendeley-tags = {patterns,resource,workflow},
number = {BETA Working Paper Series, WP 127},
title = {{Workflow Resource Patterns}},
year = {2004}
}
@inbook{Eder1996,
abstract = {Process-oriented workflow systems require transactional support in  order to guarantee consistent and reliable execution of business processes  in a multi-user and non failure free environment. Classical  (ACID) transactions are too constraining for long-lived computations,  like workflow applications. Therefore, transaction relevant requirements  of such applications are investigated and the basic concepts of a  new kind of transactions - workflow transactions - are presented. The  motivation is to integrate advanced transaction concepts into workflow  models in order to define and support a transaction based execution  of process-oriented workflows.  1},
annote = {Art\'{\i}culo viejo que presenta las limitaciones ACID de los sitemas de workflow},
author = {Eder, Johann and Liebhart, Walter},
booktitle = {Workflow Handbook},
file = {::},
keywords = {transactions,workflow},
mendeley-tags = {transactions,workflow},
pages = {157--163},
title = {{Workflow Transactions}},
url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.21.7110},
year = {1996}
}
